[antlr-interest] Organization of complex template structures

[Mike Pagel]

Hi there,

I am wondering how to best go about structuring complex sets of string 
templates. As I understand the current mechanisms, a template group is 
pretty much a class with its templates being the class methods. You can 
build inheritance structures between groups and thereby overriding 
templates (the methods) and call super group (class) templates.

This allows to build up some structure in terms of reusing basic 
templates and if required specialize certain pieces. But in the end, you 
always call a template (method) that is part of or being inherited by a 
specific leaf template group (class). Once the thread of control is 
within a template group there is no means to call templates in other 
groups, except for the groups which belong to inheritance line of the 
leaf group (if I'm not missing anything).

So far I find this limiting, e.g. if my model describes (Java) classes 
and I want to generate the class code. Then my leaf template group may 
be a "class.stg" with all kinds of templates like "generateMethods()" 
and "generateAttributes()". The implementation of those template now 
should invoke templates from a group "Methods.stg" and another group 
"Attributes.stg". (This example may not be pressing the issue but it's 
easy to follow.)

Now I cannot derive "Class.stg" from both other groups, nor can I 
somehow call into these groups (like calling static members functions of 
another class in code). What would be a good way to express this with 
the current mechanisms or is there actually a limitation?

Thanks a lot,
Mike