* src/lalr.c (traverse): Use arrays instead of pointers.

[bison.git] / doc / bison.1

diff --git a/doc/bison.1 b/doc/bison.1
index 7ce9d397610e824fac9020573de9505f5d0279fc..927a128f8a0a31654c15984e592d3f11272e7a3f 100644 (file)
--- a/doc/bison.1
+++ b/doc/bison.1
@@ -10,12 +10,24 @@ bison \- GNU Project parser generator (yacc replacement)
 ] [
 .B \-d
 ] [
 ] [
 .B \-d
 ] [

-.B \-\-defines
+.BI \-\-defines= defines-file
+] [
+.B \-g
+] [
+.BI \-\-graph= graph-file
+] [
+.B \-k
+] [
+.B \-\-token-table

 ] [
 .B \-l
 ] [
 .B \-\-no-lines
 ] [
 ] [
 .B \-l
 ] [
 .B \-\-no-lines
 ] [

+.B \-n
+] [
+.B \-\-no-parser
+] [

 .BI \-o " outfile"
 ] [
 .BI \-\-output-file= outfile
 .BI \-o " outfile"
 ] [
 .BI \-\-output-file= outfile


@@ -63,13 +75,22 @@ Unlike
 .IR yacc ,
 the generated files do not have fixed names, but instead use the prefix
 of the input file.
 .IR yacc ,
 the generated files do not have fixed names, but instead use the prefix
 of the input file.

+Moreover, if you need to put 
+.IR C++
+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
 For instance, a grammar description file named

-.B parse.y
+.B parse.yxx

 would produce the generated parser in a file named
 would produce the generated parser in a file named

-.BR parse.tab.c ,
+.BR parse.tab.cxx ,

 instead of
 .IR yacc 's
 instead of
 .IR yacc 's

-.BR y.tab.c .
+.BR y.tab.c 
+or old 
+.IR Bison
+versions
+.BR parse.tab.c .

 .PP
 This description of the options that can be given to
 .I bison
 .PP
 This description of the options that can be given to
 .I bison


@@ -106,8 +127,6 @@ chosen as if the input file were named
 .B \-d
 .br
 .ns
 .B \-d
 .br
 .ns

-.TP
-.B \-\-defines

 Write an extra output file containing macro definitions for the token
 type names defined in the grammar and the semantic value type
 .BR YYSTYPE ,
 Write an extra output file containing macro definitions for the token
 type names defined in the grammar and the semantic value type
 .BR YYSTYPE ,


@@ -128,6 +147,48 @@ in a separate source file, because
 needs to be able to refer to token type codes and the variable
 .BR yylval .
 .TP
 needs to be able to refer to token type codes and the variable
 .BR yylval .
 .TP

+.BI \-\-defines= defines-file
+The behaviour of
+.BI \-\-defines 
+is the same than 
+.BI \-d 
+option. 
+The only difference is that it has an optionnal argument which is 
+the name of the output filename.
+.TP
+.BI \-g
+.br
+.ns
+Output a VCG definition of the LALR(1) grammar automaton computed by
+Bison. If the grammar file is 
+.BR foo.y
+, the VCG output file will be
+.BR foo.vcg .
+.TP
+.BI \-\-graph= graph-file
+The behaviour of 
+.BI \-\-graph 
+is the same than
+.BI \-g
+option. The only difference is that it has an optionnal argument which 
+is the name of the output graph filename.
+.TP
+.B \-k
+.br
+.ns
+.TP
+.B \-\-token-table
+This switch causes the \fIname\fB.tab.c\fR output to include a list of
+token names in order by their token numbers;  this is defined in the array
+.IR yytname .
+Also generated
+are #defines for
+.IR YYNTOKENS ,
+.IR YYNNTS ,
+.IR YYNRULES ,
+and
+.IR YYNSTATES .
+.TP

 .B \-l
 .br
 .ns
 .B \-l
 .br
 .ns


@@ -143,6 +204,17 @@ 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.
 .TP
 grammar file.  This option causes them to associate errors with the
 parser file, treating it an independent source file in its own right.
 .TP

+.B \-n
+.br
+.ns
+.TP
+.B \-\-no-parser
+Do not generate the parser code into the output;  generate only
+declarations.  The generated \fIname\fB.tab.c\fR file will have only
+constant declarations.  In addition, a \fIname\fB.act\fR file is
+generated containing a switch statement body containing all the
+translated actions.
+.TP

 .BI \-o " outfile"
 .br
 .ns
 .BI \-o " outfile"
 .br
 .ns


@@ -174,7 +246,7 @@ The precise list of symbols renamed is
 .BR yylex ,
 .BR yyerror ,
 .BR yylval ,
 .BR yylex ,
 .BR yyerror ,
 .BR yylval ,

-.BR yychar , 
+.BR yychar ,

 and
 .BR yydebug .
 .sp
 and
 .BR yydebug .
 .sp


@@ -191,7 +263,7 @@ and so on.
 .TP
 .B \-\-debug
 Output a definition of the macro
 .TP
 .B \-\-debug
 Output a definition of the macro

-.B YYDEBUG 
+.B YYDEBUG

 into the parser file,
 so that the debugging facilities are compiled.
 .TP
 into the parser file,
 so that the debugging facilities are compiled.
 .TP


@@ -270,14 +342,21 @@ bison \-y $*
 .ft R
 .sp
 .RE
 .ft R
 .sp
 .RE

-.PP
-The long-named options can be introduced with `+' as well as `\-\-',
-for compatibility with previous releases.  Eventually support for `+'
-will be removed, because it is incompatible with the POSIX.2 standard.

 .SH FILES
 .SH FILES

-/usr/local/lib/bison.simple    simple parser
+/usr/local/share/bison/bison.simple    simple parser

 .br
 .br

-/usr/local/lib/bison.hairy     complicated parser
+/usr/local/share/bison/bison.hairy     complicated parser
+.SH "ENVIRONMENT VARIABLES"
+.TP
+.SM BISON_SIMPLE
+If this is set, it specifies the location in which the
+.B bison.simple
+parser can be found.
+.TP
+.SM BISON_HAIRY
+If this is set, it specifies the location in which the
+.B bison.hairy
+parser can be found.

 .SH SEE ALSO
 .IR yacc (1)
 .br
 .SH SEE ALSO
 .IR yacc (1)
 .br


@@ -290,4 +369,3 @@ in the
 source distribution.
 .SH DIAGNOSTICS
 Self explanatory.
 source distribution.
 .SH DIAGNOSTICS
 Self explanatory.

-