[antlr-interest] Re: make rules for *.g -> outputs

[lgcraymer]

Bryan--

The basic dependency is that treewalkers (and parsers, if in a
separate file from the lexer) depend on both the .g and a .txt file. 
You could resort to naming conventions for import/export vocabularies
and pattern substitutions in the make rules; I don't see any simpler
solution other than explicitly listing the dependencies for each
generated file.

--Loring


--- In antlr-interest at yahoogroups.com, "Bryan Ewbank" <ewbank at s...> wrote:
> Hi Folks,
> 
> I'm trying to figure out makefile rules for files generation using
ANTLR,
> and have run into the question of how to handle the *TokenType.txt (and
> .hpp) files in a general way.  The rules for .g.cpp and .g.hpp are
> relatively easy - as are those for grammar inheritance - but the
> TokenType.txt files are problematic because of how they flow from
grammar to
> grammar.
> 
> Any ideas, suggestions, etc?
> 
> - Bryan Ewbank
> "The best tool for requirements analysis and design is a crayon"





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/antlr-interest/

<*> To unsubscribe from this group, send an email to:
    antlr-interest-unsubscribe at yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/