/external/antlr/tool/src/main/java/org/antlr/tool/ |
D | CompositeGrammar.java | 210 List<Grammar> grammars = t.getPostOrderedGrammarList(); in getDelegates() local 211 grammars.remove(grammars.size()-1); // remove g (last one) in getDelegates() 212 return grammars; in getDelegates() 221 List<Grammar> grammars = new ArrayList<Grammar>(); in getDirectDelegates() local 224 grammars.add(child.grammar); in getDirectDelegates() 226 return grammars; in getDirectDelegates() 246 List<Grammar> grammars = new ArrayList<Grammar>(); in getDelegators() local 251 grammars.add(0, p.grammar); // add to head so in order later in getDelegators() 254 return grammars; in getDelegators() 291 List<Grammar> grammars = subtreeRoot.getPreOrderedGrammarList(); in getAllImportedRules() local [all …]
|
D | CompositeGrammarTree.java | 117 List<Grammar> grammars = new ArrayList<Grammar>(); in getPostOrderedGrammarList() local 118 _getPostOrderedGrammarList(grammars); in getPostOrderedGrammarList() 119 return grammars; in getPostOrderedGrammarList() 123 protected void _getPostOrderedGrammarList(List<Grammar> grammars) { in _getPostOrderedGrammarList() argument 126 child._getPostOrderedGrammarList(grammars); in _getPostOrderedGrammarList() 128 grammars.add(this.grammar); in _getPostOrderedGrammarList() 133 List<Grammar> grammars = new ArrayList<Grammar>(); in getPreOrderedGrammarList() local 134 _getPreOrderedGrammarList(grammars); in getPreOrderedGrammarList() 135 return grammars; in getPreOrderedGrammarList() 138 protected void _getPreOrderedGrammarList(List<Grammar> grammars) { in _getPreOrderedGrammarList() argument [all …]
|
/external/antlr/antlr3-maven-plugin/src/site/apt/examples/ |
D | libraries.apt | 4 as well as the ability to divide up functional components of large grammars. However it has 9 your grammar files in certain cases. If you have grammars that both use the import 13 location of your imported grammars and ANTLR will not find any vocabulary files in 16 The <<<.tokens>>> files for any grammars are generated within the same output directory structure 19 …where it is placing the generated <<<.java>>> files. Hence when you locate the grammars that gener…
|
D | import.apt | 3 In order to have the ANTLR plugin automatically locate and use grammars used 8 For a default layout, place your import grammars in the directory: <<<src/main/antlr3/imports>>>
|
D | simple.apt | 25 import grammars under <<<src/main/antlr3/imports>>> will be analyzed and converted to
|
/external/antlr/runtime/Ruby/lib/antlr3/test/ |
D | functional.rb | 81 if g = grammars[ name.to_s ] 83 grammars.delete( name.to_s ) 101 def grammars method 106 grammars.length
|
/external/antlr/antlr3-maven-plugin/src/site/apt/ |
D | usage.apt.vm | 3 The ANTLR 3 plugin for Maven can generate parsers for any number of grammars in 23 … +--- imports/ user-created .tokens files and .g files that are imported by other grammars 57 Note that you can create multiple executions, and thus build some grammars with
|
D | index.apt | 28 use version 3.1.3 of the plugin, you will build your grammars using version 3.1.3 of the 49 +--- imports/ .g files that are imported by other grammars.
|
/external/antlr/runtime/ObjC/Framework/ |
D | README.rtf | 20 …e plugin has not been updated to recognize the new recommended file extensions for ANTLR grammars:\ 22 \cf0 Parsers and combined grammars: .g generate NameLexer.(h|m) and NameParser.(h|m) files\ 25 Parser grammars (alternatively): .gp generate NameParser.(h|m) files\
|
/external/ply/ply/ |
D | PKG-INFO | 13 uses LALR(1) parsing which is efficient and well suited for larger grammars. 16 productions, precedence rules, error recovery, and support for ambiguous grammars.
|
D | ANNOUNCE | 24 precedence rules, and ambiguous grammars. 27 better suited to large grammars, and which has a number of nice
|
D | README.md | 51 precedence specifiers, and moderately ambiguous grammars. 54 better suited to large grammars, and which has a number of nice 66 PLY can be used to parse grammars consisting of several hundred
|
/external/antlr/gunit/ |
D | README.txt | 47 gUnit is an unit testing framework for ANTLR grammars. It provides a 48 simple way to write and run automated tests for grammars in a manner
|
/external/antlr/antlr-ant/main/antlr3-task/ |
D | Readme.txt | 4 Dependency check for composed grammars added. 13 introduction of composed grammars, e.g. "import T.g".
|
/external/antlr/runtime/Delphi/ |
D | README.TXT | 55 For some grammars, especially tree grammars, the code that is generated is not 63 when using this target. Please check out the Delphi sample grammars in the 86 Obviously, any custom actions inside your grammars should be written in the 94 names of rules in your grammars differ by more than only case. For example, if 105 grammars for examples):
|
/external/antlr/antlr3-maven-archetype/src/main/resources/archetype-resources/src/main/antlr3/imports/ |
D | Ruleb.g | 3 // This is just here to show that import grammars are stored in their
|
/external/antlr/tool/ |
D | CHANGES.txt | 135 time landmine occasionally with huge grammars; fails over to backtracking 145 * Sam Harwell ported all v2 grammars to v3! 387 * Fixed ANTLR-374. Was caused by moved of grammars. %foo() stuff didn't work 418 imported grammars, it will run antlr on them. 424 checker (what grammars depend on etc...). Totally independent of any 458 Made filter mode valid for tree grammars and have it automatically set 672 for delegate grammars. Fixes ANTLR-302 732 grammars would cause a null ptr exception. Fixes ANTLR-292. 741 * Improved unit testing so that each test suite executes and builds grammars 874 * Fixed ANTLR-237. updated -depend to know about imported grammars. [all …]
|
/external/antlr/antlr3-maven-archetype/src/main/resources/archetype-resources/src/main/antlr3/ |
D | TParser.g | 30 // simle demo parser. We do the import to show where imported grammars should be
|
/external/antlr/runtime/Python/ |
D | ChangeLog | 11 generated code, so (simple) grammars can be executed as standalone
|
/external/libchrome/third_party/ply/ |
D | README | 49 precedence specifiers, and moderately ambiguous grammars. 52 better suited to large grammars, and which has a number of nice 64 PLY can be used to parse grammars consisting of several hundred
|
/external/antlr/runtime/Python3/ |
D | ChangeLog | 31 generated code, so (simple) grammars can be executed as standalone
|
/external/antlr/runtime/JavaScript/build/ |
D | README | 41 grammars that have recoverable problems.)
|
/external/antlr/runtime/C/ |
D | README | 80 ANTLR v3 sample grammars: 112 handles many more grammars than v2 does. In practice, it means you 133 You can do combined lexer/parser grammars again (ala PCCTS) both lexer 472 * tree grammars also can do rewrite=true for output=template. 479 * You get a warning for tree grammars that do rewrite=true and 668 * TreeParser suffix no longer generated for tree grammars 854 * line numbers for lexers in combined grammars are now reported correctly. 874 FooLexer.java. tree grammars generate FooTreeParser.java 1058 * memoize option for grammars, rules, blocks. Remove -nomemo cmd-line option 1496 * /* epsilon */ is not printed now when printing out grammars with empty alts [all …]
|
/external/antlr/runtime/ActionScript/project/src/org/antlr/runtime/ |
D | Parser.as | 31 /** A parser for TokenStreams. "parser grammars" result in a subclass
|
D | RecognizerSharedState.as | 5 * shared among multiple grammars; e.g., when one grammar imports another.
|