On 7/13/06, J. Merrill <[EMAIL PROTECTED]> wrote:
Are you annoyed that they used different keywords (Overridable vs Virtual,
NotOverridable vs Sealed), or are you annoyed at the default they chose for
VB.Net (when overriding a virtual method, it defaults to the method being
virtual, while declaring a new method defaults to Sealed)?
It's true that they might have chosen the same keywords that C# has, given that it's a new language with new concepts;
but one could argue that they chose "more meaningful" or "more English-like" or "less
computer-sciencey" names for VB.Net because of the "less geeky" nature of many old-VB programmers.
At 10:51 AM 7/8/2006, Stoyan Damov wrote
>[ranting]
...
Actually I don't know what am I annoyed at :) I could care less about
VB.NET. I guess I was just tired and grumpy the night I posted this :)
But hey, there's always a reason to yell at Microsoft! :) For example,
my VS 2005 simply disappeared (sliently crashed) several times today
as I was typing code (disappearing while using the Windows Forms
designer is something I can live with). I guess it happened because it
was 13th. Those fucks! :) Where's my SP1? ;(
Cheers,
Stoyan
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
