Re: Managing multiple instances
- From: Andrew McDonagh <news@xxxxxxxxx>
- Date: Sun, 30 Apr 2006 20:19:28 +0100
H. S. Lahman wrote:
Responding to Stocks...
When other parts of the application need to access a particular
instance of a specific object they request the object by a type
enumeration and provide the instance number of that object that is
requested. Multiple instances of the same object may be kept in the
data structure. I did not design this and don't believe in "all the
core application classes should inherit from X and they all should be
stored in the SAME data structure" but I have to work with it. So an
object is stored and retrieved according to a class identifier and the
instance number of objects with that class identifer.
OK, but that means you have a fundamental architectural problem. You are going to have to decide whether to change the architecture or bandage the symptoms. Changing the architecture is probably going to result in a substantial "shotgun refactoring".
changing architecture is not a refactoring - its rewriting.
.
- References:
- Managing multiple instances
- From: Benjamin M. Stocks
- Re: Managing multiple instances
- From: H. S. Lahman
- Managing multiple instances
- Prev by Date: Re: Managing multiple instances
- Previous by thread: Re: Managing multiple instances
- Next by thread: Re: Alien design paradigm to alleviate "software crisis"
- Index(es):
Relevant Pages
|