The usual way to invoke Bison is as follows:
Here infile is the grammar file name, which usually ends in `.y'. The parser file's name is made by replacing the `.y' with `.tab.c'. Thus, the `bison foo.y' filename yields `foo.tab.c', and the `bison hack/foo.y' filename yields `hack/foo.tab.c'.
Bison supports both traditional single-letter options and mnemonic long option names. Long option names are indicated with `--' instead of `-'. Abbreviations for option names are allowed as long as they are unique. When a long option takes an argument, like `--file-prefix', connect the option name and the argument with `='.
Here is a list of options that can be used with Bison, alphabetized by short option. It is followed by a cross key alphabetized by long option.
YYSTYPE, as well as a few
externvariable declarations. If the parser output file is named `name.c' then this file is named `name.h'. This output file is essential if you wish to put the definition of
yylexin a separate source file, because
yylexneeds to be able to refer to token type codes and the variable
yylval. See section Semantic Values of Tokens.
#linepreprocessor commands in the parser file. Ordinarily Bison 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 as an independent source file in its own right.
#definedirectives and static variable declarations. This option also tells Bison to write the C code for the grammar actions into a file named `filename.act', in the form of a brace-surrounded body fit for a
yydebug. For example, if you use `-p c', the names become
clex, and so on. See section Multiple Parsers in the Same Program.
%rawwas specified. See section Bison Declaration Summary.
YYDEBUGinto the parser file, so that the debugging facilities are compiled. See section Debugging Your Parser.
bison -y $*
Here is a list of options, alphabetized by long option, to help you find the corresponding short option.
The command line syntax for Bison on VMS is a variant of the usual Bison command syntax--adapted to fit VMS conventions.
To find the VMS equivalent for any Bison option, start with the long option, and substitute a `/' for the leading `--', and substitute a `_' for each `-' in the name of the long option. For example, the following invocation under VMS:
bison /debug/name_prefix=bar foo.y
is equivalent to the following command under POSIX.
bison --debug --name-prefix=bar foo.y
The VMS file system does not permit filenames such as `foo.tab.c'. In the above example, the output file would instead be named `foo_tab.c'.