No subject

seems that the VB compiler (mbas) isn't up to compiling class
assemblies
just yet.  Microsoft did in fact write the VB namespace in VB.NET, and
uses aspects of the VB.NET language that aren't available in C#.  So,
in
order for mono to have a complete implementation of the base class,
we're either going to have to change how the C# language works
slightly,
write parts of the namespace in MSIL, or convert everything over and
use
the VB compiler when it matures.

 

However, right now it's my opinion that we should wait for the
compiler
to get to a point where it's usable for compiling class libraries,
then
start porting over the VB namespace to VB.  This will help in testing
the compiler as well as get the namespace in the right language.  Of
course, this is just my opinion, and I'd like to hear what some of the
big guys have to say about it.

 

When/if work starts on the VB namespace in VB, I'm more than ready to
jump in and start implementing/converting parts of it.

 

Ryan

 

 

 

________________________________

From: mono-devel-list-admin at lists.ximian.com 
[mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of Dennis
Hayes
Sent: Sunday, July 18, 2004 9:45 PM
To: mono-devel-list at lists.ximian.com 
Subject: [Mono-devel-list] VB.NET runtime

 

Currently our VB runtime is written in C#.

I have heard rumer that MS implments Microsoft.VisualBasic in VB, and
that due to differences in the languages, we will need to convert this
namespace to VB for complete compatablity.

Is this correct?
I am about to test some tools that convert between VB and C#, should I
add a MS.VB.VB to CVS and start converting the code?

Is this needed or useful?
Dennis

 

________________________________

Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard
<http://us.rd.yahoo.com/mail_us/taglines/spamguard/*http:/promotions.yah

oo.com/new_mail/static/protection.html> .