Teoman Haliloglu wrote: > > Case-by-case seems more straightforward. > > What is the abstraction? > > It sound like you are modeling a data storage system rather than real > > world objects. > > Yes,
This one word answer is my first clue that the analysis/design needs re-worked. > the idea is to pack a many to many implementation (in fact two, another > one inherting this with start/end times in the cross) and write my "real > life" classes using this package. (So, write less code for each many-to-many > implementation, for example to retrieve all the orders of a specific > customer within a certain period of time). My question is, will that be of > any help, or complicate things more, as far as you can think of? If you have code that you think will be duplicated, one way is to define a class as a datatype and declare your properties using that datatype. Another way to include a lot of classmethods is multiple inheritance. If you have some recurring data structure, see whether you can define a datatype for it. That is usually my first choice.
