AW: [mono-vb] Development on MSVB library - EX "VB Class status"

[Jochen Wezel]

To warm up the soap, again: Eventually it is a mad idea, but let's see =
your feedback...

Our current major unsolved problems for MSVB library is
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
- no support of optional parameters in MSC
- no support of modules in MSC
- the guys developing MSC don't want to include anything which would =
help us in these 2 topics

The current "solution" would be to rewrite the complete library again if =
the MBAS compiler has got a fine status for this task.

Now, my idea:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Is it possible to create a new compiler based on MSC which only extends =
it for support of the required features?=20
Maybe, it would be a great point to better compete against the original =
since C# would allow often demanded features from the VB world ;-)=20

-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: Sonntag, 27. Juni 2004 12:47
An: s.blomfield@cox.net; Mono-vb@lists.ximian.com
Betreff: RE: [Mono-devel-list] Re: [mono-vb] VB Class status

Hey Scott,

The compiler is written in C#, but you could start to help with just =
trying to compile your VB.NET programs with our compiler, and report any =
problems, ideally with test cases that show the problem :).
This way the compiler should come forth a lot quicker...

Greetz,
-- Rob.

> -----Original Message-----
> From: Scott Blomfield [mailto:s.blomfield@cox.net]
> Sent: Saturday, June 26, 2004 11:57 PM
> To: Mono-vb@lists.ximian.com
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
> Of course. Doing something unhelpful would be ... Silly =3D)
>=20
> I was just letting folks know if it comes to pass that any part of the =

> compiler is written in VB.NET then shoot me an email, not suggesting a =

> revolution. The project has come very far under their excellent=20
> leadership and support, and I am certain that without it the project=20
> would falter and come along much slower if at all.
>=20
>=20
> Cheers,
>=20
> Scott
>=20
> -----Original Message-----
> From: mono-vb-admin@lists.ximian.com
> [mailto:mono-vb-admin@lists.ximian.com] On Behalf Of=20
> Rob.Tillie@Student.tUL.EDU
> Sent: Saturday, June 26, 2004 3:03 AM
> To: s.blomfield@cox.net; Mono-vb@lists.ximian.com
> Subject: RE: [Mono-devel-list] Re: [mono-vb] VB Class status
>=20
>=20
> Hello all,
>=20
> The porting isn't the problem. Surely there's some convert tool from=20
> 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=20
> to us. Let's wait and hear what the leaders (Rafael, Jambunathan,=20
> 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=20
> > porting
>=20
> > 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=20
> > new
>=20
> > code though.
> >
> > -----Original Message-----
> > From: mono-vb-admin@lists.ximian.com=20
> > [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=20
> > in programming both VB.NET and C#, and would be glad to do whatever=20
> > I can
>=20
> > to help.  Of course, having a legion of VB developers won't do us=20
> > 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=20
> > just porting the C# code will take a while.  However, it seems like=20
> > a worthwhile cause to do this so as to not pollute the C# compiler=20
> > or language with constructions necessary to create the VisualBasic=20
> > namespace.
> >
> > Additionally it would create a sample library of VisualBasic code,=20
> > and
>=20
> > probably provide a lot of feedback to the people working on the VB=20
> > 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#=20
> > 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=20
> > it would take some time to rewrite everything to VB. I helped a bit=20
> > 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=20
> > class was already started in C#, but I think in the long run it=20
> > would be a wiser decision.
> >
> > For all we know, there might be future changes in the future that=20
> > may require other VB specific features to properly compile that we=20
> > would have to create custom exceptions for or otherwise modify how=20
> > the IL is
>=20
> > generated from the source code.  It seems better in my view at least =

> > to hedge against this possible condition and implement the library=20
> > 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=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
> >
> > 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=20
> > probably don't need a special syntax for this.  We can have an=20
> > 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=20
> > 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
>=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