>>>>> On Mon, 3 Feb 2003 11:11:03 -0900 (AKST), Arthur Corliss ><[EMAIL PROTECTED]> said:
> On Tue, 28 Jan 2003, Henrik Tougaard wrote: >> When I saw the modulename I immediately thought of a 'has-a' relationship. >> In UML that is called Agrregation. >> The name ought to convey sa better idea of what the module does - >> Class::Aggregate is IMHO just too generic. I can't think of a better name >> though. > I know, that's my quandry as well. Let's face it: there's no reasonably > short name that's going to be desriptive enough. So, if not that, how about: > Class::Lite (since it's a relatively light-weight implementation) > Class::Orderly (referencing the point of the container relationship > for destruction purposes) > Hell, call it Class::Foo, for all I care, I'd just like to get an officially > sanctioned module that does what I want and can be reused across all the > Curses::* modules I'm working on. I'm getting tired of duplicating code. . . > Any ideas? Before you call it Foo or Bar or Lite, try something that resembles your intent even if not being really descriptive. Orderly looks fine to me as do the following: Class::Event Class::Eventable Class::Hierarchy Class::EHierarchy Class::ECHierarchy -- andreas
