Basics:
DONE 2/2/2010
A tree pattern matcher should work for all. record options on way down. We need
a way to count elements too for things like repeated options spec.
• FILE_AND_GRAMMAR_NAME_DIFFER
• LEXER_RULES_NOT_ALLOWED
• PARSER_RULES_NOT_ALLOWED
• CANNOT_ALIAS_TOKENS_IN_LEXER
• ARGS_ON_TOKEN_REF
• ILLEGAL_OPTION
• REWRITE_OR_OP_WITH_NO_OUTPUT_OPTION
• NO_RULES
• REWRITE_FOR_MULTI_ELEMENT_ALT
• HETERO_ILLEGAL_IN_REWRITE_ALT
• AST_OP_WITH_NON_AST_OUTPUT_OPTION
• AST_OP_IN_ALT_WITH_REWRITE
• CONFLICTING_OPTION_IN_TREE_FILTER
• WILDCARD_AS_ROOT
• INVALID_IMPORT
• TOKEN_VOCAB_IN_DELEGATE
• IMPORT_NAME_CLASH
• new errors:
• REPEATED_PREQUEL; repeated options or tokens spec (since we
allow in any order now)
• TOKEN_NAMES_MUST_START_UPPER
it's awesome. no side effects and just a list of checks. don't have to search
code for random spots I do checking.
should I push the trunk to antlr.org so people can follow along?
Ter
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org/mailman/listinfo/antlr-dev
