It's related enough :)
Doru
On Wed, Mar 12, 2014 at 2:15 PM, Esteban A. Maringolo
wrote:
> Not exactly the same, but related... one of the features I REALLY miss
> from the Dolphin Smalltalk debugger is the listing of the stack
> variables in the debugger. This way, I could see, manipulate and
Not exactly the same, but related... one of the features I REALLY miss
from the Dolphin Smalltalk debugger is the listing of the stack
variables in the debugger. This way, I could see, manipulate and
inspect intermediate objects, assigned to temporal variables like
_stack1, _stack2, etc. [1]
That
Hi,
Yes, these are all points for research. It is these things that can make
Pharo define its own ground and change dramatically the meaning of
programming. There is so much we can do in this space.
If anyone wants to start playing let me know so that we can coordinate.
Cheers,
Doru
On Tue, M
The MIT Curl debugger in their integrated IDE is for an expression-based
language
and so your are able to "watch" expressions of your own devising as you
step through code - and drill down graphically into structured values such
as object instances ; there is now an eclipse "plug-in" version of th
Friedrich Dominicus wrote:
anyway. Has anyone considered adding filtering to the Debugger (in my
case the Glamorous Debugger) in a way that not all instance variables
values are shown in the value pane?
Well a kind of watch as in other debuggers. You just can "ask" to watch
e.g field firstName b
anyway. Has anyone considered adding filtering to the Debugger (in my
case the Glamorous Debugger) in a way that not all instance variables
values are shown in the value pane?
Well a kind of watch as in other debuggers. You just can "ask" to watch
e.g field firstName but not lastName or something
