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:
59 Output a definition of the macro YYDEBUG into the parser file,
60 so that the debugging facilities are compiled.
65 Write an extra output file containing macro definitions for the token
66 type names defined in the grammar and the semantic value type
67 YYSTYPE, as well as a extern variable declarations.
69 If the parser output file is named "name.c" then this file
72 This output file is essential if you wish to put the definition of
73 yylex in a separate source file, because yylex needs to
74 be able to refer to token type codes and the variable
84 Specify a prefix to use for all Bison output file names. The names are
85 chosen as if the input file were named prefix.c
91 Equivalent to /OUTPUT=y_tab.c; the parser output file is called
92 y_tab.c, and the other outputs are called y.output and
93 y_tab.h. The purpose of this switch is to imitate Yacc's output
94 file name conventions. The /YACC qualifier is functionally equivalent
95 to /FIXED_OUTFILES. The following command definition will
96 work as a substitute for Yacc:
99 $YACC:==BISON/FIXED_OUTFILES
109 Rename the external symbols used in the parser so that they start with
110 "prefix" instead of "yy". The precise list of symbols renamed
111 is yyparse, yylex, yyerror, yylval, yychar and yydebug.
113 For example, if you use /NAME_PREFIX="c", the names become cparse,
120 Don't put any "#line" preprocessor commands in the parser file.
121 Ordinarily Bison puts them in the parser file so that the C compiler
122 and debuggers will associate errors with your source file, the
123 grammar file. This option causes them to associate errors with the
124 parser file, treating it an independent source file in its own right.
129 Do not generate the parser code into the output; generate only
130 declarations. The generated name_tab.c file will have only
131 constant declarations. In addition, a name.act file is
132 generated containing a switch statement body containing all the
142 Specify the name "outfile" for the parser file.
147 When this switch is specified, the .tab.h file defines the tokens to
148 have the bison token numbers rather than the yacc compatible numbers.
149 To employ this switch you would have to have your own parser.
154 This switch causes the name_tab.c output to include a list of
155 token names in order by their token numbers; this is defined in the array
156 yytname. Also generated are #defines for YYNTOKENS, YYNNTS, YYNRULES,
163 Write an extra output file containing verbose descriptions of the
164 parser states and what is done for each type of look-ahead token in
167 This file also describes all the conflicts, both those resolved by
168 operator precedence and the unresolved ones.
170 The file's name is made by removing _tab.c or .c from
171 the parser output file name, and adding .output instead.
173 Therefore, if the input file is foo.y, then the parser file is
174 called foo_tab.c by default. As a consequence, the verbose
175 output file is called foo.output.
180 Print the version number of Bison.