> >> Just to make sure I understand this correctly... As technically
> >> subclass
> >> is never generated if it already exists in the target location, is it
> >> fair
> >> to rephrase this as "'cgen' must allow a different destination folder
> >> for
> >> subclasses and superclasses"?
> >
> > That would work too. That would be handy in that new classes would get
> > generated there, and then I'd add them to my version control.
> >
Seems to me like this would be redundant on functionality that can
just as easily be achieved using existing ant tasks. Rather than have
the potentially confusing option to split the output dirs, I would
have the option to simply not generate wrappers, or better, to leave
it as it is... the more pure the generator the better, I think...
This archive was generated by hypermail 2.0.0 : Wed Apr 27 2005 - 23:54:53 EDT