Re: .NET haters ought to get a kick out of this


Bob Butler wrote:
"Russ Rose" <russrose@xxxxxxxxxxx> wrote in message
news:CuidnTRtUrrf8MPYnZ2dnUVZ_sqdnZ2d@xxxxxxxxxxx
<cut>
Dim x as Integer = 0


That is a poor example, since as always VB.NET will intialize the
variable to 0 anyway (C# won't intialize local variables).

A better example would be:

Dim x As Integer = 10

And, it is much more concise then:

Dim x As Integer
x = 10

For x as Integer = 1 to 10

This statement limits the scope of x to the for block. It is
considered good programming practice in most modern languages to limit
the scope of a variable to the smallest possible scope.

Try ..Catch.. Finally

There are some situtations where that's nice; others where it's not. It's a
wash as far as I'm concerend.


Where is it "not"? And why?

Auto indent, auto complete, auto wash...

The auto-indent "feature" of VS.Net I find annoying as hell because it will
not indent the way I normally do. Not sure what you mean by auto complete
(at least that is different than VB6) or auto wash.

Stay in your little .Net haters world if you want, but break when
value changes is not worth missing out on the rest.

BTW, hating VB.Net and hating dotnet are very different things. dotnet as a
platform, for web development, has a lot of nice things. VB.Net has no
reason to exist.

That's a laugh. I've worked full time with .NET for the last 4 years,
and in that time I have never produced a full scale web app. I've
written dialers, servers, and desktop applications...

--
Tom Shelton

.

Loading