[antlr-interest] RE: updated "antlr 2 bashing list...

[brian-l-smith at uiowa.edu]

Here are some more feature requests:

* Provide a mechanism to explicitly label a rule as a start rule. The current
mechanism of "if it isn't referenced, it is a start rule" has caused me a lot of
frustration in the past. This also forces us to create "dummy" start rules. For
example, imagine a grammar for a Java-like language. I might want to be able to
start my parser at any of the following rules:
    sourceFile, classOrInterface, method, attribute,
    feature, declaration, expression, statement,
    packageDeclaration, importDeclaration, etc.
Currently, I have to create an extra "start rule" for each of these rules. I
would rather prefix the original rules with a "start" keyword. 
    
* In the generated code, make all rules that aren't start rules private instead
of public. In general, I believe that almost all of the generated methods should
be private by default.

* Provide a way to prevent the generation of constructors for the generated
parser and lexer classes. Usually I want to create my own special public
constructor(s) with additional arguments, and I don't want to have all of the
generated constructors around.

- Brian






 
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/