2 .! RUNOFF source file for BISON.HLP
4 .! This is a RUNOFF input file which will produce a VMS help file
5 .! for the VMS HELP library.
7 .! Eric Youngdale and Wilfred J. Hansen (wjh+@cmu.edu).
19 The BISON command invokes the GNU BISON parser generator.
30 Here file-spec is the grammar file name, which usually ends in
31 .y. The parser file's name is made by replacing the .y
32 with _tab.c. Thus, the command bison foo.y yields
39 The following is the list of available qualifiers for BISON:
60 define the macro YYDEBUG to 1 if it is not already defined,
61 so that the debugging facilities are compiled.
66 Write an extra output file containing macro definitions for the token
67 type names defined in the grammar and the semantic value type
68 YYSTYPE, as well as a extern variable declarations.
70 If the parser output file is named "name.c" then this file
73 This output file is essential if you wish to put the definition of
74 yylex in a separate source file, because yylex needs to
75 be able to refer to token type codes and the variable
85 Specify a prefix to use for all Bison output file names. The names are
86 chosen as if the input file were named prefix.c
92 Equivalent to /OUTPUT=y_tab.c; the parser output file is called
93 y_tab.c, and the other outputs are called y.output and
94 y_tab.h. The purpose of this switch is to imitate Yacc's output
95 file name conventions. The /YACC qualifier is functionally equivalent
96 to /FIXED_OUTFILES. The following command definition will
97 work as a substitute for Yacc:
100 $YACC:==BISON/FIXED_OUTFILES
110 Rename the external symbols used in the parser so that they start with
111 "prefix" instead of "yy". The precise list of symbols renamed
112 is yyparse, yylex, yyerror, yylval, yychar and yydebug.
114 For example, if you use /NAME_PREFIX="c", the names become cparse,
121 Don't put any "#line" preprocessor commands in the parser file.
122 Ordinarily Bison puts them in the parser file so that the C compiler
123 and debuggers will associate errors with your source file, the
124 grammar file. This option causes them to associate errors with the
125 parser file, treating it an independent source file in its own right.
130 Do not generate the parser code into the output; generate only
131 declarations. The generated name_tab.c file will have only
132 constant declarations. In addition, a name.act file is
133 generated containing a switch statement body containing all the
143 Specify the name "outfile" for the parser file.
148 When this switch is specified, the .tab.h file defines the tokens to
149 have the bison token numbers rather than the yacc compatible numbers.
150 To employ this switch you would have to have your own parser.
155 This switch causes the name_tab.c output to include a list of
156 token names in order by their token numbers; this is defined in the array
157 yytname. Also generated are #defines for YYNTOKENS, YYNNTS, YYNRULES,
164 Write an extra output file containing verbose descriptions of the
165 parser states and what is done for each type of look-ahead token in
168 This file also describes all the conflicts, both those resolved by
169 operator precedence and the unresolved ones.
171 The file's name is made by removing _tab.c or .c from
172 the parser output file name, and adding .output instead.
174 Therefore, if the input file is foo.y, then the parser file is
175 called foo_tab.c by default. As a consequence, the verbose
176 output file is called foo.output.
181 Print the version number of Bison.