ansaurus

Question

Best practice to create typed collections/lists with internal or private Add, Remove functionality?

Answer 1

+3 A:

EDIT

Since you want...

...to be able to add to the collection / list internally or privately

you can have a private IList<T> you'll be adding objects to, and the ReadOnlyCollection<T> will be a wrapper around this list. Since it's a wrapper, all changes to an underlying list will be reflected in this read-only collection.

Anton Gogolev 2010-01-22 11:09:52

I would like to be able to add to the collection / list internally or privately. The ReadOnlyCollection appears to only let you construct with the final items.

Nanook 2010-01-22 11:19:32

+1 - I was considering keeping a reference to the list used to construct the ReadOnlyCollection. I'm pleased you already confirmed it. In this case, I have nested collections which would still make it a little awkward, but still viable. I am going to persue a base collection type with protected only add and remove methods as this would be the best solution to my current issue.

Nanook 2010-01-22 11:29:51

You're right, it is the correct answer. If I inherit from ReadOnlyCollection<string> and accept a List<string> as my constructor parameter, I can keep a reference in my class and also pass it to the base constructor. I can then add internal Add and Remove methods to my class. This would allow me to nest custom classes if required (instead of using string).

Nanook 2010-01-22 11:47:37

Answer 2

A:

Expose interface:

IEnumerable<T>

dario-g 2010-01-22 23:00:58

ansaurus

tags:

views:

answers:

Best practice to create typed collections/lists with internal or private Add, Remove functionality?

related questions