Stongly typed collections

[Bucky]

I've been wondering, what is the advantage of a strongly-typed
collection (inheriting the CollectionBase and overriding the Add
method and the default property)? Is it:

a.) Easier to code with, because all the casting is done in the
Collection itself, and you get the advantage of IntelliSense and such,
b.) Increased runtime speed, because there isn't any boxing and
unboxing done to convert the types to and from an Object,
c.) Both, or
d.) Bucky, what are you smoking?

Now that I think about it, B seems a little ridiculous, since the
type is cast to and from an Object whether it's done in a
strongly typed collection or if it's done outside the collection.

Or maybe I have no idea what I'm talking about.

 

[divil]

http://www.zdnet.com.au/builder/program/windows/story/0,2000035027,20269412,00.htm

Maybe that'll help. I don't know if they are faster in any way, I would doubt it in fact. I just use them because if I'm exposing a collection of something, I don't want joe user adding just anything to it and breaking my code

Also, designers know what to do with it if it's a strongly-typed collection.

 

[Bucky]

From that article:

However, the advantages of a strongly typed collection
class include its ability to hold only instances of the type you
designate and to add custom functionality particular to the class
it holds. This ensures that the items in the collection can be
worked with efficiently, without having to cast to the correct type.

I understand now... that makes a lot of sense. Thanks.

So I guess the answer would be D, huh?