RE: [VB4Linux-Dev] hey I guess so.

[Scott B. <js...@go...>]

On Mon, 20 Nov 2000, Abhijit Paithankar wrote:

> The debugger should be in VB.
> This also means, we should be able to reverse interpret the C code.
> 
> another way would be to parse the VB code itself and make sure there are (if
> possible) no erors (syntax or logical)in the code even before putting it
> thro vb2c.
We should beable to add debugging functions on the C side with no problem,
again like Python and Tcl have. (always look to the past to see the
future)


> 
> >
> > As this project is meant to be a near-exact port of Visual Basic
> > (besides the
> > binary result and OS), the debugger should be VB.....
> >
> > > I think it best to keep this part of the code as hi-level as
> > > possible.  And again it does not matter if it is not compiled or
> > > compilable for awhile, without a good solid core (vb2c) it's useless
> > > anyway.  The debugger is upfor debate on if it should be in C or
> > > VB.  Though in the Tcl/Tk and Python world their debuggers are mixed.
> 
> _______________________________________________
> VB4Linux-Dev mailing list
> VB4...@li...
> http://lists.sourceforge.net/mailman/listinfo/vb4linux-dev
> 
>