M
mike3
Hi.
I saw this discussion thread:
http://stackoverflow.com/questions/...boilerplate-code-for-polymorphic-objects-in-c
It mentions something very similar to what I've got, and the answer
that has the most thumbs up is saying "if you need to clone, the
design is bad", and of course, says nothing about what the _good_
design would be. In my case, what I have is an object called
"LevelGenerator" that has a number of derived types, each of which can
generate a different kind of level and store parameters for the level
generation.
The trick is that there is also an object that holds specifications of
levels in a full level system, and associated with each level
specification is a LevelGenerator. But suppose we need to make many of
these specifiers, each with the same LevelGenerator. It would be
easier to clone the LevelGenerator for each one, so that way, if we
want to delete one of them, we can delete the corresponding
LevelGenerator in that delete without affecting anything else. But
Cloning is BAD!!!!
I saw this discussion thread:
http://stackoverflow.com/questions/...boilerplate-code-for-polymorphic-objects-in-c
It mentions something very similar to what I've got, and the answer
that has the most thumbs up is saying "if you need to clone, the
design is bad", and of course, says nothing about what the _good_
design would be. In my case, what I have is an object called
"LevelGenerator" that has a number of derived types, each of which can
generate a different kind of level and store parameters for the level
generation.
The trick is that there is also an object that holds specifications of
levels in a full level system, and associated with each level
specification is a LevelGenerator. But suppose we need to make many of
these specifiers, each with the same LevelGenerator. It would be
easier to clone the LevelGenerator for each one, so that way, if we
want to delete one of them, we can delete the corresponding
LevelGenerator in that delete without affecting anything else. But
Cloning is BAD!!!!