Syntax 4.2
- Introduction
- Sample Output
- Concepts
- File Structure
- Lexer
- Production Rules
- Error Management
- Lexer Driven Parsing
Syntax maven plugin reference
The following parameters can be entered through the configuration.
Configuration Argument | Required | Description |
---|---|---|
<sourceFile> | Yes | This is the specification of the Syntax file to be used. Add the extension. |
<outputFile> | Yes | This is the specification of the file to be generated. Add the extension. |
<includeFile> | No | When not provided and external include is desired, the include file name will be changed. |
<reportFile> | No | The report file is an HTML file with the results of the analysis of the grammar, and its results, together with a summary. |
<skeletonFie> | No | If specified, the given file should contain the parse code. |
<bundleFile> | No | If provided, it is a properties file for java with the error codes |
<language> | No | If omitted, java is assumed. Valid values are C, java, pascal. |
<algorithm> | No | When omitted, lalr is assumed. Valid values are slr, lalr. |
<externalInclude> | No | Decide if a file with extenal definitions is desired. Not valid for java. |
<verbose> | No | Produces additional display output. |
<debug> | No | Produces parser phase output. |
<emitLine> | No | For C, do you want #line statements pointing to the .syntax file? |
<packed> | No | Default to tabular. Valid values are packed, tabular. Use tabular for a clearer parser table. Not recommended for large grammars. |
<driver> | No | Default to parser. Valid values are parser, scanner. |
<margin> | No | Used to change the emitted code’s right margin. Should be greater than 80 |
<indent> | No | Used to change the emitted code’s indentation. Default is 2 |