1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
|
BISON(1) User Commands BISON(1)
NAME s
bison - GNU Project parser generator (yacc replacement)
n
SYNOPSIS 2
j:l. [OPTION]... FILE
4
DESCRIPTION
Bison is a parser generator in the style of yacc(1). It
should be upwardly compatible with input files designed
for yacc.
Input files should follow the yacc convention of ending
in .y. Unlike yacc, the generated files do not have
fixed names, but instead use the prefix of the input
file. Moreover, if you need to put 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 parse.yxx would produce
the generated parser in a file named parse.tab.cxx,
instead of yacc's y.tab.c or old Bison version's
parse.tab.c.
This description of the options that can be given to
bison is adapted from the node Invocation in the
bison.texinfo manual, which should be taken as authori-
tative.
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-pre-
fix, connect the option name and the argument with =.
Generate LALR(1) and GLR parsers.
Mandatory arguments to long options are mandatory for
short options too. The same is true for optional argu-
ments.
Operation modes:
-h, --help
display this help and exit
-V, --version
output version information and exit
--print-localedir
output directory containing locale-dependent data
--print-datadir
output directory containing skeletons and XSLT
-y, --yacc
emulate POSIX Yacc
-W, --warnings=[CATEGORY]
report the warnings falling in CATEGORY
Parser:
-L, --language=LANGUAGE
specify the output programming language (this is
an experimental feature)
-S, --skeleton=FILE
specify the skeleton to use
-t, --debug
instrument the parser for debugging
--locations
enable locations computation
-p, --name-prefix=PREFIX
prepend PREFIX to the external symbols
-l, --no-lines
don't generate `#line' directives
-k, --token-table
include a table of token names
Output:
--defines[=FILE]
also produce a header file
-d likewise but cannot specify FILE (for POSIX Yacc)
-r, --report=THINGS
also produce details on the automaton
--report-file=FILE
write report to FILE
-v, --verbose
same as `--report=state'
-b, --file-prefix=PREFIX
specify a PREFIX for output files
-o, --output=FILE
leave output to FILE
-g, --graph[=FILE]
also output a graph of the automaton
-x, --xml[=FILE]
also output an XML report of the automaton (the
XML schema is experimental)
Warning categories include:
`midrule-values'
unset or unused midrule values
`yacc' incompatibilities with POSIX YACC
`all' all the warnings
`no-CATEGORY'
turn off warnings in CATEGORY
`none' turn off all the warnings
`error'
treat warnings as errors
THINGS is a list of comma separated words that can
include:
`state'
describe the states
`itemset'
complete the core item sets with their closure
`lookahead'
explicitly associate lookahead tokens to items
`solved'
describe shift/reduce conflicts solving
`all' include all the above information
`none' disable the report
AUTHOR
Written by Robert Corbett and Richard Stallman.
Copyright (C) 2008 Free Software Foundation, Inc. This
is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.
REPORTING BUGS
Report bugs to <bug-bison@gnu.org>.
SEE ALSO
lex(1), flex(1), yacc(1).
The full documentation for bison is maintained as a Tex-
info manual. If the info and bison programs are prop-
erly installed at your site, the command
info bison
should give you access to the complete manual.
bison 2.4.1 December 2008 BISON(1)
|
