All uses of XCALLOC, XMALLOC, and XREALLOC changed to use new macros

[bison.git] / doc / bison.1

diff --git a/doc/bison.1 b/doc/bison.1
index ebcd396cde17ef30436a24e7265dd3ecc2f94d8e..f7ebbdcbaabb6dc271d571f88d24aedc248fdfa1 100644 (file)
--- a/doc/bison.1
+++ b/doc/bison.1
@@ -10,7 +10,11 @@ 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 \-k
 ] [


@@ -71,10 +75,10 @@ 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++
+Moreover, if you need to put
+.I C++

 code in the input file, you can end his name by a C++-like extension
 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 
+(.ypp or .y++), then bison will follow your extension to name the

 output file (.cpp or .c++).
 For instance, a grammar description file named
 .B parse.yxx
 output file (.cpp or .c++).
 For instance, a grammar description file named
 .B parse.yxx


@@ -82,10 +86,10 @@ would produce the generated parser in a file named
 .BR parse.tab.cxx ,
 instead of
 .IR yacc 's
 .BR parse.tab.cxx ,
 instead of
 .IR yacc 's

-.BR y.tab.c 
-or old 
-.IR Bison
-versions
+.B y.tab.c
+or old
+.I Bison
+version's

 .BR parse.tab.c .
 .PP
 This description of the options that can be given to
 .BR parse.tab.c .
 .PP
 This description of the options that can be given to


@@ -118,13 +122,11 @@ Specify a prefix to use for all
 .I bison
 output file names.  The names are
 chosen as if the input file were named
 .I bison
 output file names.  The names are
 chosen as if the input file were named

-\fIfile-prefix\fB.c\fR.
+\fIfile-prefix\fP\fB.c\fP.

 .TP
 .B \-d
 .br
 .ns
 .TP
 .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 ,


@@ -133,10 +135,10 @@ as well as a few
 variable declarations.
 .sp
 If the parser output file is named
 variable declarations.
 .sp
 If the parser output file is named

-\fIname\fB.c\fR
+.IB name .c

 then this file
 is named
 then this file
 is named

-\fIname\fB.h\fR.
+\fIname\fP\fB.h\fP.

 .sp
 This output file is essential if you wish to put the definition of
 .B yylex
 .sp
 This output file is essential if you wish to put the definition of
 .B yylex


@@ -145,13 +147,41 @@ 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 behavior of
+.B \-\-defines
+is the same than
+.B \-d
+option.
+The only difference is that it has an optional 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 behavior of
+.BI \-\-graph
+is the same than
+.BI \-g
+option.  The only difference is that it has an optional argument which
+is the name of the output graph filename.
+.TP

 .B \-k
 .br
 .ns
 .TP
 .B \-\-token-table
 .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
+This switch causes the
+.IB name .tab.c
+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 yytname .
 Also generated
 are #defines for


@@ -181,9 +211,13 @@ parser file, treating it an independent source file in its own right.
 .ns
 .TP
 .B \-\-no-parser
 .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
+Do not generate the parser code into the output; generate only
+declarations.  The generated
+.IB name .tab.c
+file will have only
+constant declarations.  In addition, a
+.IB name .act
+file is

 generated containing a switch statement body containing all the
 translated actions.
 .TP
 generated containing a switch statement body containing all the
 translated actions.
 .TP


@@ -234,9 +268,9 @@ and so on.
 .ns
 .TP
 .B \-\-debug
 .ns
 .TP
 .B \-\-debug

-Output a definition of the macro
+In the parser file, define the macro

 .B YYDEBUG
 .B YYDEBUG

-into the parser file,
+to 1 if it is not already defined,

 so that the debugging facilities are compiled.
 .TP
 .B \-v
 so that the debugging facilities are compiled.
 .TP
 .B \-v


@@ -315,9 +349,9 @@ bison \-y $*
 .sp
 .RE
 .SH FILES
 .sp
 .RE
 .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
 .SH "ENVIRONMENT VARIABLES"
 .TP
 .SM BISON_SIMPLE