[VB4Linux-Dev] (no subject)

[<abh...@ma...>]

	

> could we leverage the Tcl/Tk debug environment for our 
> debugging program if
> we code vb2c in Tcl/Tk? any idea how? In that case it could be 
> of help...
> 
> Well coding it in a higher level language like Tcl would give you a
> speeder turn around in development time as you know (and more people
> could support it).  We could write hooks in C (in the support libs we
will
> need anyway) to help with debugging and could generate the calls for
them
> on the fly in Tcl from the debugger (It would be easier for "code
> injection" with it), so yes it could help.  
> 
> There are a couple of other options for debugging.  We could 
> generate a.out
> or elf stubs section with the debugging symbols and write and 
> extension for
> gdb.  This would take more time tho.  We could also write a VM and
have
> hooks into it for debugging.

I think it would be the best to code debugger in C.

vb apps in design stage would use pre-existing .so files to run in a
virtual environment where the debugger would be present. Once we have
to release the vb app, we shall then put it thro vb2c.

Also, about using wine libs...looks OK on the surface, but can we
emulate only a specific dll or OCX using wine?
Also, when we want to emulate them, we'd need to have them
first...which means we need to have M$ VisualBasic installed on the win
partition first...before VB4Linux can use the OCX files...which is not
what should be.
...which could mean that we have to have native OCX files....





---------------------------------------------------------------
This Message was Powered by Xcel Communications
Sign up for your FREE EMAIL account today at http://www.mailroom.com
Give your FAX machine an email address http://www.faxroom.com