'pim_test' parses the given source file and lists the derivation tree on stdout.
The source file must be conform with the language parameter. It uses the image files
of the parser and scanner tables, [Language.lim] and [Language.pim].
In the case you specify a start symbol the parsing process starts from this nonterminal.
The symbol must be specified as valid start nonterminal in [Language.sty].
If the option is omitted the parser takes the first start nonterminal.
Name | Type | Semantic |
Language | name | language name |
FileName | path | path of source file to parse |
Name | Type | Default value | Semantic |
Start | string | "" | start symbol |
charset | string | "" | source file character set ( UTF-8, UCS4, ... ) |
binmode | flag | false | scan source file in binary mode ( not with charset-option ) |
wprint | flag | false | unicode output ( on non-default character set ) |
tree | flag | true | create a derivation tree ( optimized memory representation ) |
xaron | flag | false | create a derivation tree ( lisp like representation ) |
early | flag | false | use early reduction |
prepar | string | "" | preprocessing: index~value , ... |
premac | string | "" | preprocessing: pre-defined macro , ... |
The options 'prepar' and 'premac' are only useful with styx-like preprocessing.
If your language uses the same preprocessing directives as specified in [styx.sty],
but differnt macro token identifiers and keywords, the option 'prepar' can be used to
enable preprocessing and specify the differences as a comma separated list:
The option 'premac' supports pre-defined macros in connection with
styx-like preprocessing.
Name | Type | Default value | Semantic |
PATH | path | search path for [Language.pim] and [Language.lim] |