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

Rob.Tillie@Student.tUL.EDU Rob.Tillie@Student.tUL.EDU
Sat, 26 Jun 2004 16:03:28 +0200


Agreed...

> -----Original Message-----
> From: Jochen Wezel [mailto:jwezel@compumaster.de]
> Sent: Saturday, June 26, 2004 12:59 PM
> To: Rob.Tillie@Student.tUL.EDU; s.blomfield@cox.net; Mono-
> vb@lists.ximian.com
> Subject: AW: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
> > Statements supported are 'If..Then..Else' , 'While..End While'
> > and assignment statements. Simple operators (+, -, *, /, >, <, =3D)
> > should also work. Other statements (For..Next, etc.) should be
> > quite trivial to implement.
> 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 ;-)
>=20
> Cya
> Jochen
>=20
>=20
> -----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
>=20
> Hello all,
>=20
> 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.
> 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.
>=20
> Greetz,
> -- Rob.
>=20
> > -----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
> >
> > 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.
> >
> > -----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
> >
> >
> > Well, I'm certainly willing to help.  I've got a lot of experience =
in
> > 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
> > good if the build system isn't up to the task yet.  What will it =
take
> > to get this working?
> >
> > I know that it would take a while to rebuild everything in VB, even
> > just porting the C# code will take a while.  However, it seems like =
a
> > worthwhile cause to do this so as to not pollute the C# compiler or
> > language with constructions necessary to create the VisualBasic
> > namespace.
> >
> > Additionally it would create a sample library of VisualBasic code, =
and
> > probably provide a lot of feedback to the people working on the VB
> > compiler, to ensure that all the issues are worked out.
> >
> > Ryan Gregg
> > Intellidev
> >
> > -----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
> >
> >  The problem is I guess that more people on this list program in C#
> > rather then VB. Another problem is that the build system isn't =
ready
> > yet to build VB.NET dll's, as MBAS is not quit ready. Besides that =
it
> > would take some time to rewrite everything to VB. I helped a bit in
> > the implementation, but I don't know enough VB to program in it.
> >
> > Greetz,
> > -- Rob.
> >
> > -----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
> >
> > 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
> > class was already started in C#, but I think in the long run it =
would
> > be a wiser decision.
> >
> > For all we know, there might be future changes in the future that =
may
> > require other VB specific features to properly compile that we =
would
> > 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
> > to hedge against this possible condition and implement the library =
in
> VB.
> >
> > Ryan Gregg
> > Intellidev
> >
> > -----Original Message-----
> > From: mono-devel-list-admin@lists.ximian.com
> > [mailto:mono-devel-list-admin@lists.ximian.com] On Behalf Of Raja R
> > 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
> >
> > Hi,
> >
> > "A Rafael D Teixeira" <rafaelteixeirabr@hotmail.com> writes:
> >
> > > 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).
> >
> > If it is just for us to implement Microsoft.VisualBasic in C#, we
> > probably don't need a special syntax for this.  We can have an
> > internal attribute named
> >
> >   Microsoft.VisualBasic.Mono__DefaultValueAttribute
> >
> > And either 'mcs' or ParameterBuilder.SetCustomAttribute() can =
handle
> > this specially.  However, it won't work with CSC -- I don't see =
that
> > as a major problem, though.
> >
> > If you want to provide a general facility for expressing this CIL
> > capability in C#, then, yeah -- it's a problem :-)
> >
> > - Hari
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> > _______________________________________________
> > 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
> _______________________________________________
> Mono-vb mailing list
> Mono-vb@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-vb