Re: Where I can find a detailed Boo Compiler specification

As a developer o mono's mbas VB.NET compiler, I can say your worst
problem is not compiling your VB6 source code, but rather deal with
VB6 form and project data and, the worst, the many ActiveX controls
and classes you may be using.

The top problem with the Visual Studio.NET converter is that even your
own VB6 classes (that you have to compile in many DLLs, for layering
purposes, or because of size limitations imposed by the compiler) are
wrapped as COM objects and used as such in the other parts of your
solution, because it can't determine correctly what may need to be so,
or not, and DOESN'T GIVE YOU A CHANCE TO CHOOSE.

Anyway, I hope you can cook something that better helps with your  big
project conversion

Have fun,


On Fri, 4 Feb 2005 02:28:13 -0500, Ricardo Balda 
<ricbalda-PkbjNfxxIARBDgjK7y7TUQ@xxxxxxxxxxxxxxxx> wrote:
>  
> Hi there: 
>   
> I have a VB6 app with 60,000 of code lines, I try the Visual Studio .NET
> converter by the amount of warnings is a long term project that I can't
> afford. We think it is better that use the ANTLR parse generator to compile
> the VB6 code to CLR code I know that Boo, C# and VB.NET is different to VB6,
> but the time to convert the code is enormous, may be the shortest path to do
> that is first a VB6.NET compiler and then make a gradual convertion to Boo
> or C# or VB.NET, if you look at the internet forums you can see the a lot of
> VB6 programmers asking for a compiler, you made a excelente work with the
> Boo and if you would like to advise me to accomplish this project I'm in
> debt with you.
>  
> The best Regards 
> Ricardo Balda 
>   


-- 
Rafael "Monoman" Teixeira
---------------------------------------
I'm trying to become a "Rosh Gadol" before my own eyes. 
See http://www.joelonsoftware.com/items/2004/12/06.html for enlightment.