[plt-scheme] PLT's debugger philosophy

If you're asking about the Debug button, I don't think there's any
particular "philosophy" behind it.  It's just something I've hacked up
and various other people (mainly Matthew) have helped to maintain.

Actually, I don't think the Debug button works so differently from
what you've described in MIT Scheme, except that you need to enable it
explicitly when you start the program.  (This is because the
breakpoint and introspection capabilities require source annotation,
which incurs some overhead.)  The other differences are primarily in
the user interface.

If you're asking about the Stepper (and Macro Stepper), then that's a
different discussion, but their creators could respond better than I.

Greg

On 2/12/08, Grant Rettke <grettke at acm.org> wrote:
> Last week I watched a movie that demonstrated how the MIT Scheme
> debugger functions. Apparently when an error occurs, you can start the
> debugger at which point you've got access to that stack frame at the
> location of the error at which point you can evaluate expressions and
> muck about with the environment if you desire. I haven't explored it
> any further than watching.
>
> The thing that struck me is that it is different the how the debugger
> works in DrScheme.
>
> Do these two approaches reflect two Scheme debugger philosophies?
>
> What is the philosophy behind PLT's debugger?
> _________________________________________________
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>