Re: A History of Variables
- From: "qubit" <lauraeaves@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Tue, 13 Oct 2009 16:58:36 -0500
I'm not a java programmer, but how do you intend to handle scope in such a
debugger? If you have gone out of a block or function, you are no longer
interested in -- nor can you be sure of the value of -- stack variables in that
function, as that space can be overwritten by other function calls. Or am I
answering my own question?...
Actually, this might be relevant from a debugging standpoint if someone tries
to use a pointer to a local -- or is that not supported in java?
I really should glance over a java tutorial... After C++ I hear it is easy to
learn, but I never took the time to do it.
--le
----- Original Message -----
From: Andreas Stefik
To: programmingblind@xxxxxxxxxxxxx
Sent: Tuesday, October 13, 2009 3:04 PM
Subject: A History of Variables
Hello folks,
My student and I are working on part of our auditory debugger (in Sodbeans)
related to its ability to "go backwards." Essentially, our debugger allows you
to see (or hear) any value of any variable that has previously been set in the
program. We have a number of ideas about how we can structure the audio portion
of the debugger, but we're curious, if such a feature were available to you,
how would you like it to work. As such, we pose the following question:
Suppose your debugger could execute in reverse and return, in audio, the
value of any variable that has ever been set in your program. Using only the
keyboard, how would you like to access such information?
While much of the backend is now implemented, we haven't implemented the user
interface yet, so any ideas, no matter how wacky, are very welcome.
Stefik
Other related posts:
