Posted by
timothy
on from the boy-are-my-lips-tired dept.
prostoalex writes "Scott Mitchell published his rather extensive examination of data structures in C# 2.0 (parts 1, 2, 3, 4, 5 and 6 add up to more than a hundred printed pages)."
Re:No Fibonacci Heap?
by
Elwood+P+Dowd
·
· Score: 3, Interesting
It's just a body count issue. If Microsoft had twice the time or twice the number of people, C# 2.0 would have had twice the number of new features. Lots of good stuff got jettisoned. Everywhere you look on blogs.msdn.com, folks are talking about what they woulda/coulda/shoulda done with more time.
In the time it took this guy to write the article, perhaps he could have added these data structures to C#/.NET's laughably impoverished System.Collections class. The big thing in the new, upcoming version 2.0 is that they're introducing, wait for it, linked lists.
Still no sign of anything resembling a set/multiset, or a tree structure, let alone something like a heap. The documentation is equally sad, making no mention of big-O complexity. The comparison with Java, both in content and documentation, is depressing.
I like C# as a language, but the CS illiteracy of the libraries is annoying and inconvenient. The lack of a concept of a tree means that there's no automatic way to show an XML DOM tree with a TreeControl. They both have independently-developed, incompatible, although largely equivalent, tree representations.
Also, note that the SortedList class does not implement the IList interface, and none of the shipped System.Collections classes implement their own CollectionBase.
It's just a body count issue. If Microsoft had twice the time or twice the number of people, C# 2.0 would have had twice the number of new features. Lots of good stuff got jettisoned. Everywhere you look on blogs.msdn.com, folks are talking about what they woulda/coulda/shoulda done with more time.
There are no trails. There are no trees out here.
In the time it took this guy to write the article, perhaps he could have added these data structures to C#/.NET's laughably impoverished System.Collections class. The big thing in the new, upcoming version 2.0 is that they're introducing, wait for it, linked lists.
Still no sign of anything resembling a set/multiset, or a tree structure, let alone something like a heap. The documentation is equally sad, making no mention of big-O complexity. The comparison with Java, both in content and documentation, is depressing.
I like C# as a language, but the CS illiteracy of the libraries is annoying and inconvenient. The lack of a concept of a tree means that there's no automatic way to show an XML DOM tree with a TreeControl. They both have independently-developed, incompatible, although largely equivalent, tree representations.
Also, note that the SortedList class does not implement the IList interface, and none of the shipped System.Collections classes implement their own CollectionBase.