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

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

>how do we divide the work?
>FROM: Abhijit PaithankarDATE: 11/17/2000
 
>I think instead of giving 2 options, we could have just a VB2C
>interpreter.
Anyone looked at this: http://www.naken.cc/vb2c/

>CHM Reader/Viewer and CHM Compiler
>Syntax colorer and GUI i.e. GUI and the editor
>VB2C interpreter and Syntax checker
What about holding off until a base vb2c is done, then code most of the
tools in the language itself, or do them in VB now and use them as a test 
for the translator?

>other tasks like runtime debugger need to be thought of coz` of
>interpreting, the debugger shall need to reverse-interpret the C code to
>VB
Same as above.

>at design-time, we can emulate the Win32 API. should we make use of Wine
>where?
>that shall take care of OCX stuff.
I would use the Wine libs.... saves time and money ;-)

scott