Geoff Howard <[EMAIL PROTECTED]> writes:
> Wild proposal: merge all code into one class, named something
> very clear (like TraversableSourceHierarchyGenerator) and
> subclass that with DirectoryGenerator (or something very like
> it) and have that subclass override nothing:
>
> public class DirectoryGenerator extends
> TraversableSourceHierarchyGenerator {
>
> /**
> * Identical to superclass - class only for name/function clarity.
> **/
>
> }
>
> too crazy?
You might actually want to have some implementation specific method
names if you did this. In particular, the setLeaf, setNode issue could
have nicer semantics for the directory implementation with setFile,
setDirectory methods being added that did nothing but forward the calls
on as appropriate. (Polymorphism for method names :-)...
