is a parser generator in the style of
It should be upwardly compatible with input files designed
Input files should follow the
convention of ending in
the generated files do not have fixed names, but instead use the prefix
of the input file.
Moreover, if you need to put
code in the input file, you can end his name by a C++-like extension
(.ypp or .y++), then bison will follow your extension to name the
output file (.cpp or .c++).
For instance, a grammar description file named
would produce the generated parser in a file named
This description of the options that can be given to
is adapted from the node
manual, which should be taken as authoritative.
supports both traditional single-letter options and mnemonic long
option names. Long option names are indicated with
Abbreviations for option names are allowed as long as they
are unique. When a long option takes an argument, like
connect the option name and the argument with
Specify a prefix to use for all
output file names. The names are
chosen as if the input file were named
Write an extra output file containing macro definitions for the token
type names defined in the grammar and the semantic value type
as well as a few
If the parser output file is named
then this file
This output file is essential if you wish to put the definition of
in a separate source file, because
needs to be able to refer to token type codes and the variable
The behavior of
is the same than
The only difference is that it has an optional argument which is
the name of the output filename.
Output a VCG definition of the LALR(1) grammar automaton computed by
Bison. If the grammar file is
, the VCG output file will be
The behavior of
is the same than
option. The only difference is that it has an optional argument which
is the name of the output graph filename.
This switch causes the
output to include a list of
token names in order by their token numbers; this is defined in the array
are #defines for
Don't put any
preprocessor commands in the parser file.
puts them in the parser file so that the C compiler
and debuggers will associate errors with your source file, the
grammar file. This option causes them to associate errors with the
parser file, treating it an independent source file in its own right.
Do not generate the parser code into the output; generate only
declarations. The generated
file will have only
constant declarations. In addition, a
generated containing a switch statement body containing all the
Specify the name
for the parser file.
The other output files' names are constructed from
as described under the
Rename the external symbols used in the parser so that they start with
The precise list of symbols renamed is
For example, if you use
the names become
and so on.
In the parser file, define the macro
to 1 if it is not already defined,
so that the debugging facilities are compiled.
Write an extra output file containing verbose descriptions of the
parser states and what is done for each type of look-ahead token in
This file also describes all the conflicts, both those resolved by
operator precedence and the unresolved ones.
The file's name is made by removing
from the parser output file name, and adding
Therefore, if the input file is
then the parser file is called
by default. As a consequence, the verbose
output file is called
Print the version number of
Print a summary of the options to
the parser output file is called
and the other outputs are called
The purpose of this switch is to imitate
output file name conventions.
Thus, the following shell script can substitute for
and is often installed as
bison -y "$@"
Bison Reference Manual,
included as the file