Re: Managing multiple instances
- From: "Benjamin M. Stocks" <stocksb@xxxxxxxx>
- Date: 30 Apr 2006 10:18:56 -0700
Now it seems to me that you should either access A via its B owner (in
other words get specific B first, then use it to get its A instance), or
that B shouldn't be the creator of A. It's hard to tell though, without
more specific description.
Amen!!!!!! I joined the project after this data structure was already
in use so I can't argue a "throw away" principle but I'm trying to
modify it so it's a less bad idea.
But you hit it: B creates A (which adds the instances of A to the data
structure) and then other objects in what I am calling the client code
also use those instances of A. Rather than going through B they go to
this data structure and pull references to those instances of A and use
them.
Kind regards,
Ben
.
- References:
- Managing multiple instances
- From: Benjamin M. Stocks
- Re: Managing multiple instances
- From: AndyW
- Re: Managing multiple instances
- From: Benjamin M. Stocks
- Re: Managing multiple instances
- From: Sasa
- Managing multiple instances
- Prev by Date: Re: Managing multiple instances
- Next by Date: Re: Managing multiple instances
- Previous by thread: Re: Managing multiple instances
- Next by thread: Re: Managing multiple instances
- Index(es):