3 bison \- GNU Project parser generator (yacc replacement)
9 .BI \-\-file-prefix= file-prefix
21 .BI \-\-output-file= outfile
25 .BI \-\-name-prefix= prefix
47 .B \-\-fixed-output-files
52 is a parser generator in the style of
54 It should be upwardly compatible with input files designed
58 Input files should follow the
60 convention of ending in
64 the generated files do not have fixed names, but instead use the prefix
66 For instance, a grammar description file named
68 would produce the generated parser in a file named
74 This description of the options that can be given to
76 is adapted from the node
80 manual, which should be taken as authoritative.
83 supports both traditional single-letter options and mnemonic long
84 option names. Long option names are indicated with
88 Abbreviations for option names are allowed as long as they
89 are unique. When a long option takes an argument, like
91 connect the option name and the argument with
95 .BI \-b " file-prefix"
99 .BI \-\-file-prefix= file-prefix
100 Specify a prefix to use for all
102 output file names. The names are
103 chosen as if the input file were named
104 \fIfile-prefix\fB.c\fR.
111 Write an extra output file containing macro definitions for the token
112 type names defined in the grammar and the semantic value type
116 variable declarations.
118 If the parser output file is named
124 This output file is essential if you wish to put the definition of
126 in a separate source file, because
128 needs to be able to refer to token type codes and the variable
138 preprocessor commands in the parser file.
141 puts them in the parser file so that the C compiler
142 and debuggers will associate errors with your source file, the
143 grammar file. This option causes them to associate errors with the
144 parser file, treating it an independent source file in its own right.
150 .BI \-\-output-file= outfile
155 The other output files' names are constructed from
157 as described under the
167 .BI \-\-name-prefix= prefix
168 Rename the external symbols used in the parser so that they start with
172 The precise list of symbols renamed is
181 For example, if you use
193 Output a definition of the macro
195 into the parser file,
196 so that the debugging facilities are compiled.
203 Write an extra output file containing verbose descriptions of the
204 parser states and what is done for each type of look-ahead token in
207 This file also describes all the conflicts, both those resolved by
208 operator precedence and the unresolved ones.
210 The file's name is made by removing
214 from the parser output file name, and adding
218 Therefore, if the input file is
220 then the parser file is called
222 by default. As a consequence, the verbose
223 output file is called
231 Print the version number of
240 Print a summary of the options to
252 .B \-\-fixed-output-files
255 the parser output file is called
257 and the other outputs are called
261 The purpose of this switch is to imitate
263 output file name conventions.
264 Thus, the following shell script can substitute for
274 The long-named options can be introduced with `+' as well as `\-\-',
275 for compatibility with previous releases. Eventually support for `+'
276 will be removed, because it is incompatible with the POSIX.2 standard.
278 /usr/local/lib/bison.simple simple parser
280 /usr/local/lib/bison.hairy complicated parser
285 .IR "Bison Reference Manual" ,