Mike,
I am bit slow lately (a result of a coding marathon on a customer
project) ... could you post some examples of what variables you'd have
in the context of a superclass and subclass template? By
subclass/superclass/baseclass do you mean fully qualified names?
[OT] How about we kill the default single class template all together.
One has to really hate himself and his peers to use it on a project.
Andrus
On May 12, 2005, at 9:09 PM, Mike Kienenberger wrote:
> Here's what I'm thinking for class and package attributes.
>
> Rather than having the relative class/superclass/package/superpackage
> attributes, how about absolute attributes of
> subclass/superclass/baseclass
> and package?
>
> For singleclass generation, it could either set subclass/superclass to
> the
> same value, or I could add an additional singleclass/singlePackage
> attribute.
>
> I see three "wins" for this scenario. All three attributes are
> available in
> all templates. Moving templated code between the templates won't
> require
> any changes as the attributes are all absolute. And I think it'll be
> less
> confusing to end-users.
>
> -Mike
This archive was generated by hypermail 2.0.0 : Thu May 12 2005 - 23:30:10 EDT