>> Why is C# using the wrong terminology? (Or at the very least, really
>> misleading?)
>
> Yeah, I don't really know.
>
> Java has a /interface/ called "list", which represents "a list of
> things". It then provides several different implementations of this
> interface, including "LinkedList" and "ArrayList".
>
> C# seems to have copied this terminology, having an IList interface and
> a List class which implements it. But it's certainly nothing to do with
> linked lists (which don't implement IList at all, and hence don't even
> *offer* element indexing as a build-in method).

It's worse...

C# actually *has* an ArrayList class. But that was written before they 
added generics. (I.e., an ArrayList holds only Objects.) So when they 
added generics, ArrayList became just List.

Yuck.

Post a reply to this message