A general purpose mechanism for organizing classes into groups with a single public interface. Modules may be nested within other modules.
Advantages:
- localizes public interface
- eliminates unneccessary ivars
- one location for init & release
- gives good starting location for test & debug
Code change 8/29/2001 --connect code removed, requiresUnique is now used differently, name & parentModule instance variables added. Connect code somewhat superflous, as it was only necessary when the connection had to be delayed. Otherwise equivalent of: requires at: ModuleName put: aModuleInstance