OpenEuphoria

Re: The Console

• Posted by Al Getz <xaxo at AOL.COM> Nov 03, 2000
• 389 views

Dave,

  What i was talking about, the windows based debugger, in full form,
would require fully parsing the Euphoria source files, including
any include .e files that needed to be debugged.  A simpler version
would require the user to specify the variables to be viewed during
the debugging process (not as nice but easier), but would still require
parsing into logical blocks at the very least, unless one could accept
the (rather harsh) restraint that each program be written with each
line containing exactly one logical block of Euphoria syntax:

  constant a,b,c,d --would be acceptable

  constant a,
           b,
           c,
           d --would not be acceptable

Because of this restraint, i would opt for a full form debugger, but
again it would have to parse completely and accurately.
Color syntax would have to be similar to a text editor, if this
is really needed?

As with a debugger in any language, once the language is parsed,
it is a simple matter to insert calls to a display
routine/pause control procedure to print out variables and wait for
user input (such as step in, step through, etc.) as well as
correlate program blocks back to original line numbers.
It would be even possible to change variables during program execution.
Of course a new trace function would be introduced, say, "wintrace(1)".

Since you have been working on parsers recently, maybe you
feel up to producing a parser to parse the Euphoria language
into a group of logical blocks of text and variable names.
If so, i'll gladly produce the GUI portion, and we will
have ourselves a windows based debugger!

If i can, i'll post a simplified example debugger soon.

Let me know your thoughts on this...

--Al