Reply to thread

Message: [QUOTE="xarax, post: 530431"] /snip/ In addition to the other comments, you should also be wary of any occurance of a switch(){} block that is used to vary the processing depending on the type of an object. Such type-dependent processing should be delegated to the child class, usually through abstract methods in the parent class. However, some purists are strongly averse to calling abstract methods within a constructor, transfering control to the uninitialized child class. With careful design and implementation, it's not all that bad, and certainly more object-oriented than using switch blocks. Having said all of that, I do have some package-private classes that are very similar to what you posted (no switch block) that are programmatically generated. The use of type codes to enumerate the various subclasses is a safety check to be sure that I *do not* add more subclasses. The set of subclasses is fixed; the type codes are an easy way to verify that subclasses are not added incompatibly. (Remember these classes are programmatically generated, rather than handwritten.) /xarax [/QUOTE]