On Tue, 1 May 2001, Dan Sugalski wrote:
> Right. What I'm thinking would be a good place to get to is a list of the
> functionality that the debugger needs to provide or have available to it
> from the interpreter, rather than the actual interface to the user. (Which
> is important, but a separate issue)
[snip]
> though. I think we're still at the "What functionality should the
> interpreter/compiler/parser provide to the person writing a debugger" phase.
Errrmmm...sorry, but let me just be clear on this. I had intended
to write this document in (more or less) the following sections:
- things that the user can do (set breakpoints, step, etc)
- implementation details of each feature in the previous section
(what data structures do we use to store breakpoints? what information is
associated with them? etc)
- the internals of the debugger; its APIs, etc.
It sounds like you don't want the first two sections. Can you
give me a better idea of what exactly you are looking for in this
document?
Incidentally, I'm not trying to dictate interface...it's just that
starting with the functionality is a convenient "handle" for figuring out
what internals the debugger will need.
Dave
