🚀 go-pugleaf

"Marc Rohloff [TeamB]" <"on request"> a �crit dans le message de news: 
1sewcl5nubmpn.dlg@dlg.marcrohloff.com...

| On 7 Apr 2006 03:01:54 -0700, Murdoc wrote:
|
| > So only initialize the collection instance if it is necessary.
| >
| > public void add(Object o)
| > {
| >     if (_collection == null)
| >         _collection = new Collection();
| >
| >     _collection.add(o);
| > }
|
| You could also do this in the property which retrieves your collection
| object.

And if you write a private read-only property, you don't have to repeat the 
same checking code everywhere.

private Collection InnerCollection
{
  get
  {
    if (collection == null)
      collection = new Collection();
    return collection;
  }
}

Then your code does things like this :

public void Add(object o)
{
  InnerCollection.Add(o);
}

public object this[int index]
{
  return InnerCollection[index];
}

public void Remove(object o)
{
  InnerCollection.Remove(o);
}

Of course, the problem that this approach brings is that you would be 
creating a collection just to find out that the indexer or the Remove method 
ends up talking to an empty, newly created, collection.

Joanna

-- 
Joanna Carter [TeamB]
Consultant Software Engineer