> From: Brad Jensen
> Microsoft is discovering some of its own inertia. The three
> million VB programmers are less than ecstatic about being shoved
> into an 'upgrade'to VB.NET that is really a different, C-based
> language, tons of stuff breaks.

Wow.  I just looked at the VB.NET specs, and it really is fundamentally
different from VB.  In fact, I suspect that most code written for VB will
not work with VB.NET.  Just the fact that parentheses are now required for
function calls is enough to cause that.  Changing the behavior of the
assignment operator is also pretty huge.  Automatic conversion between
string and numeric is gone.  Static functions are gone.  UDTs are gone.

I pity the folks who are forced to move, and given deadlines to do it.

On the other hand, I think there's a heck of an opportunity for someone if
they wanted to write a VB to VB.NET converter.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.