| Modifier and Type | Field and Description |
|---|---|
| pack-priv List |
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| protected ST | chooseWhereCyclicDFAsGo(Tool tool, CodeGenerator generator, Grammar grammar, ST recognizerST, ST cyclicDFAST)
|
| protected void | genRecognizerFile(Tool tool, CodeGenerator generator, Grammar grammar, ST outputFileST)
Overrides org. |
| protected void | genRecognizerHeaderFile(Tool tool, CodeGenerator generator, Grammar grammar, ST headerFileST, String extName)
|
| public String | getTargetCharLiteralFromANTLRCharLiteral(CodeGenerator generator, String literal)
Overrides org. |
| public String | getTargetStringLiteralFromANTLRStringLiteral(CodeGenerator generator, String literal)
Overrides org. |
| public boolean | isValidActionScope(int grammarType, String scope)
Overrides org. |
| protected void | performGrammarAnalysis(CodeGenerator
An instance of the generic code generator class. generator, Grammar The grammar that we are currently analyzing grammar)
Overrides the standard grammar analysis so we can prepare the analyser
a little differently from the other targets.
|
| strings | back to summary |
|---|---|
| pack-priv List<String> strings | |
| CTarget | back to summary |
|---|---|
| public CTarget() | |
| chooseWhereCyclicDFAsGo | back to summary |
|---|---|
| protected ST chooseWhereCyclicDFAsGo(Tool tool, CodeGenerator generator, Grammar grammar, ST recognizerST, ST cyclicDFAST) | |
| genRecognizerFile | back to summary |
|---|---|
| protected void genRecognizerFile(Tool tool, CodeGenerator generator, Grammar grammar, ST outputFileST) throws IOException Overrides org.
| |
| genRecognizerHeaderFile | back to summary |
|---|---|
| protected void genRecognizerHeaderFile(Tool tool, CodeGenerator generator, Grammar grammar, ST headerFileST, String extName) throws IOException Overrides org.
| |
| getTargetCharLiteralFromANTLRCharLiteral | back to summary |
|---|---|
| public String getTargetCharLiteralFromANTLRCharLiteral(CodeGenerator generator, String literal) Overrides org. Doc from org. Convert from an ANTLR char literal found in a grammar file to an equivalent char literal in the target language. For most languages, this means leaving 'x' as 'x'. Actually, we need to escape ' ' so that it doesn't get converted to \n by the compiler. Convert the literal to the char value and then to an appropriate target char literal. Expect single quotes around the incoming literal.
| |
| getTargetStringLiteralFromANTLRStringLiteral | back to summary |
|---|---|
| public String getTargetStringLiteralFromANTLRStringLiteral(CodeGenerator generator, String literal) Overrides org. Convert from an ANTLR string literal found in a grammar file to an equivalent string literal in the C target. Because we must support Unicode character sets and have chosen to have the lexer match UTF32 characters, then we must encode string matches to use 32 bit character arrays. Here then we must produce the C array and cater for the case where the lexer has been encoded with a string such as 'xyz\n',
| |
| isValidActionScope | back to summary |
|---|---|
| public boolean isValidActionScope(int grammarType, String scope) Overrides org. Is scope in @scope::name {action} valid for this kind of grammar? Targets like C++ may want to allow new scopes like headerfile or some such. The action names themselves are not policed at the moment so targets can add template actions w/o having to recompile ANTLR.
| |
| performGrammarAnalysis | back to summary |
|---|---|
| protected void performGrammarAnalysis(CodeGenerator generator, Grammar grammar) Overrides org. Overrides the standard grammar analysis so we can prepare the analyser a little differently from the other targets. In particular we want to influence the way the code generator makes assumptions about switchs vs ifs, vs table driven DFAs. In general, C code should be generated that has the minimum use of tables, and tha meximum use of large switch statements. This allows the optimizers to generate very efficient code, it can reduce object code size by about 30% and give about a 20% performance improvement over not doing this. Hence, for the C target only, we change the defaults here, but only if they are still set to the defaults.
| |