.NET Framework Collection Class Design
A collection is a collection. Although this may sound like an odd statement and not make much sense, it does hold some truth. If you were to take a collection of objects internally organized a certain way and another collection of objects internally organized in a different way, would you want different ways of inserting, removing, or retrieving them? For instance, if you have a basket of oranges and a shopping cart of oranges, why should you have to learn two different ways to work with those containers given that they serve the same purpose—to collect oranges to be retrieved later?
The collection classes within the .NET Framework are designed in such a way that manipulating the objects each collection ...
Get Sams Teach Yourself Visual C++® .NET in 24 Hours now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
