On 2007-11-10 12:25:39 -0800, Jon Skeet [C# MVP] <sk***@pobox.comsaid:
Bela Istok <be****@hotmail.comwrote:
>I think there is no diferences, because is an evolution from C# 2.0 to 3.0,
here is a summary of the new features:
http://dotnetwithme.blogspot.com/200...csharp-30.html
How can you list new features but claim there are no differences? The
new features *are* the differences.
I suspect a language gap? Hopefully Bela does not mean _literally_ "no
differences", but perhaps he is speaking from some sort of specific
point of view (his own perception of what's a "practical" or
"significant" difference, maybe?). He'd still be incorrect, but at
least his statement wouldn't be self-contradictory. :)
>PD: C# is only the compiler for the lenguage, the big differences are on the
Framework.
I have to disagree there. There's support in the framework for LINQ of
course, but you can use a lot of the new features of C# 3 without even
targeting .NET 3.5 - and that's what I expect a lot of people will do,
early on.
I agree with the disagreement. :) In fact, while I can't speak of C#
3.0 specifically, I myself find that in my own C# code I am more often
taking advantage of features that are new to C# 2.0 as opposed to being
new to .NET 2.0. One major exception being generic collections, but
even those are themselves as much a result of a feature new to C# 2.0
as they are simply something new for .NET 2.0.
Much of the framework stuff I'm using has been around since .NET 1.1.
It seems to me that, while they may be developed in parallel and may in
fact rely on each other in some way, surely the new features of C# 3.0
would be useful even for someone who doesn't use anything in .NET 3.5.
Pete
