Object bloat (TKitchenSink) is a symptom of failure to reconsider your design (see "Hardening of the architecture" on page 50). A class definition starts out simple and clean, but as time goes on and changes are made, it becomes larger and larger, with the class identity becoming harder to state concisely. Some of the possible actions to solve this problem are:
This isn't an exhaustive list. A rule of thumb is: if you can't give a concise human language definition of the class, you likely have a problem.
- Move some of the functions into new classes that the object would use.
- Break up the class into two or more classes.
- Rethink the class definition based on experience gained.
Click the icon to mail questions or corrections about this material to Taligent personnel.
Copyright©1995 Taligent,Inc. All rights reserved.
Generated with WebMaker