Star FSF: Microsoft's Community Promise "Empty"
Linked by Thom Holwerda on Mon 20th Jul 2009 15:54 UTC, submitted by Brandon L
Mono Project As you would have guessed, the Mono debate is long from over. Two weeks ago, Microsoft extended its legally binding and perpetual community promise to cover the C# and CLI ECMA standards, which was generally seen as a good thing for Linux-centric fans of the C# language as well as for the Mono project. The FSF has responded now, and it isn't too impressed with Microsoft's move.
E-mail Print r 8   · Read More · 49 Comment(s) http://osne.ws/gv6
Permalink for comment 374387
To read all comments associated with this story, please click here.
tuttle
Member since:
2006-03-01

What do you have against the collections library?[q]

The collections library is incomplete (almost no concurrent collections, only recently added a set class. No interface for sets, confusing and inconsistent naming).

[q]It's not like you need to import the whole thing, you only import the classes you need....


The using statement does not work for generic classes or interfaces. Try importing just System.Collections.Generic.List<T>. It is not possible.

So why bog down the System namespace with this stuff (since that's essentially equivalent to importing it by default).


Because IEnumerable is used everywhere. There are various language features (foreach, yield, LINQ) that depend on IEnumerable. So it is a core interface just like System.Array is a core class.

And the system namespace is bogged down with lots of less important stuff like the obsolete MarshalByRefObject and other remoting-related classes.

Reply Parent Bookmark Score: 3