AW: [Mono-devel-list] Re: [mono-vb] VB Class status

[Jochen Wezel]

> Statements supported are 'If..Then..Else' , 'While..End While'=20
> and assignment statements. Simple operators (+, -, *, /, >, <, =3D)=20
> should also work. Other statements (For..Next, etc.) should be=20
> quite trivial to implement.=20
As it's standing on the mono website, there are some "trivial" todos.=20

Maybe, we should focus on these easy parts of the compiler first (see =
mbparser.jay) before forcing the translation of MS.VB.dll to VB.NET and =
while waiting for statements of our other VB.NET/Mono gurus.=20

And, Rob, you can continue writing C# code ;-)

Cya
Jochen


-----Urspr=FCngliche Nachricht-----
Von: mono-vb-admin@lists.ximian.com =
[mailto:mono-vb-admin@lists.ximian.com] Im Auftrag von =
Rob.Tillie@Student.tUL.EDU
Gesendet: Samstag, 26. Juni 2004 10:03
An: s.blomfield@cox.net; Mono-vb@lists.ximian.com
Betreff: RE: [Mono-devel-list] Re: [mono-vb] VB Class status

Hello all,

The porting isn't the problem. Surely there's some convert tool from C# =
--> VB.NET. The problem is getting MBAS (Our VB.NET compiler) in a =
production-ready state so it can compile MS.VB.dll during build.=20
I'm in favor of doing the right thing now, but this decision isn't up to =
us.
Let's wait and hear what the leaders (Rafael, Jambunathan, Banirban, =
etc.) have to say, and point us in the direction they want to take.

Greetz,
-- Rob.

> -----Original Message-----
> From: Scott Blomfield [mailto:s.blomfield@cox.net]
> Sent: Saturday, June 26, 2004 5:28 AM
> To: Mono-vb@lists.ximian.com
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
> At this point in time I also would be able to assist in either porting =

> code from C# to VB.NET or writing code from scratch in VB.NET.
> Unfortunately my native C# code is not up to scratch to contribute new =

> code though.
>=20
> -----Original Message-----
> From: mono-vb-admin@lists.ximian.com
> [mailto:mono-vb-admin@lists.ximian.com] On Behalf Of Ryan Gregg
> Sent: Friday, June 25, 2004 8:33 AM
> To: Rob.Tillie@Student.tUL.EDU
> Cc: mono-vb@lists.ximian.com; mono-devel-list@lists.ximian.com
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
>=20
> Well, I'm certainly willing to help.  I've got a lot of experience in=20
> programming both VB.NET and C#, and would be glad to do whatever I can =

> to help.  Of course, having a legion of VB developers won't do us any=20
> good if the build system isn't up to the task yet.  What will it take=20
> to get this working?
>=20
> I know that it would take a while to rebuild everything in VB, even=20
> just porting the C# code will take a while.  However, it seems like a=20
> worthwhile cause to do this so as to not pollute the C# compiler or=20
> language with constructions necessary to create the VisualBasic=20
> namespace.
>=20
> Additionally it would create a sample library of VisualBasic code, and =

> probably provide a lot of feedback to the people working on the VB=20
> compiler, to ensure that all the issues are worked out.
>=20
> Ryan Gregg
> Intellidev
>=20
> -----Original Message-----
> From: Rob.Tillie@Student.tUL.EDU [mailto:Rob.Tillie@Student.tUL.EDU]
> Sent: Friday, June 25, 2004 7:25 AM
> To: Ryan Gregg
> Cc: mono-vb@lists.ximian.com; mono-devel-list@lists.ximian.com
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
>  The problem is I guess that more people on this list program in C#=20
> rather then VB. Another problem is that the build system isn't ready=20
> yet to build VB.NET dll's, as MBAS is not quit ready. Besides that it=20
> would take some time to rewrite everything to VB. I helped a bit in=20
> the implementation, but I don't know enough VB to program in it.
>=20
> Greetz,
> -- Rob.
>=20
> -----Original Message-----
> From: Ryan Gregg
> Cc: mono-vb@lists.ximian.com; mono-devel-list@lists.ximian.com
> Sent: 25-6-04 7:37
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
> Wouldn't it just make more sense to implement the VB namespace in its
> own language?   That's the approach Microsoft took when developing it,
> and granted it might be some porting work from this point since the=20
> class was already started in C#, but I think in the long run it would=20
> be a wiser decision.
>=20
> For all we know, there might be future changes in the future that may=20
> require other VB specific features to properly compile that we would=20
> have to create custom exceptions for or otherwise modify how the IL is =

> generated from the source code.  It seems better in my view at least=20
> to hedge against this possible condition and implement the library in =
VB.
>=20
> Ryan Gregg
> Intellidev
>=20
> -----Original Message-----
> From: mono-devel-list-admin@lists.ximian.com
> [mailto:mono-devel-list-admin@lists.ximian.com] On Behalf Of Raja R=20
> Harinath
> Sent: Friday, June 25, 2004 12:03 AM
> To: A Rafael D Teixeira
> Cc: mono-vb@lists.ximian.com; mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
> Hi,
>=20
> "A Rafael D Teixeira" <rafaelteixeirabr@hotmail.com> writes:
>=20
> > Kudos Raja, you went right to the point.
> >
> > The problem is (besides the MonoTODO) that if C# doesn't have the
> syntax
> > to support it, we may have to rewrite part, or the whole, of our
> library
> > in VB.NET, or put an option in mcs to specifically allow such
> extension
> > of syntax (Miguel probably wouldn't like that).
>=20
> If it is just for us to implement Microsoft.VisualBasic in C#, we=20
> probably don't need a special syntax for this.  We can have an=20
> internal attribute named
>=20
>   Microsoft.VisualBasic.Mono__DefaultValueAttribute
>=20
> And either 'mcs' or ParameterBuilder.SetCustomAttribute() can handle=20
> this specially.  However, it won't work with CSC -- I don't see that=20
> as a major problem, though.
>=20
> If you want to provide a general facility for expressing this CIL=20
> capability in C#, then, yeah -- it's a problem :-)
>=20
> - Hari
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>=20
>=20
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>=20
>=20
> _______________________________________________
> Mono-vb mailing list
> Mono-vb@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-vb
>=20
> _______________________________________________
> Mono-vb mailing list
> Mono-vb@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-vb
_______________________________________________
Mono-vb mailing list
Mono-vb@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-vb