bison man page on Ultrix

Man page or keyword search:  
man Server   3690 pages
apropos Keyword Search (all sections)
Output format
Ultrix logo
[printable version]

BISON(1)							      BISON(1)

       bison - GNU Project parser generator (yacc replacement)

       bison  [	 -b  file-prefix  ]  [	--file-prefix=file-prefix  ]  [ -d ] [
       --defines ] [ -k ] [ --token-table ] [ -l ] [ --no-lines ]  [  -n  ]  [
       --no-parser  ] [ -o outfile ] [ --output-file=outfile ] [ -p prefix ] [
       --name-prefix=prefix ] [ -r ] [ --raw ] [ -t ] [ --debug ]  [  -v  ]  [
       --verbose  ] [ -V ] [ --version ] [ -y ] [ --yacc ] [ -h ] [ --help ] [
       --fixed-output-files ] file

       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.  For instance, a grammar description file
       named parse.y would produce  the	 generated  parser  in	a  file	 named, instead of yacc's

       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 authoritative.

       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-prefix,  connect  the
       option name and the argument with =.

       -b file-prefix
	      Specify  a  prefix  to use for all bison output file names.  The
	      names are chosen as if the input file were named file-prefix.c.

	      Write an extra output file containing macro definitions for  the
	      token  type  names defined in the grammar and the semantic value
	      type YYSTYPE, as well as a few extern variable declarations.

	      If the parser output file is named  name.c  then	this  file  is
	      named name.h.

	      This  output file is essential if you wish to put the definition
	      of yylex in a separate source file, because yylex	 needs	to  be
	      able to refer to token type codes and the variable yylval.

       --raw  The  token  numbers in the name.h file are usually the Yacc com‐
	      patible translations.  If this switch is specified, Bison	 token
	      numbers  are  output instead.  (Yacc numbers start at 257 except
	      for  single  character  tokens;	Bison  assigns	token  numbers
	      sequentially for all tokens starting at 3.)

	      This  switch  causes  the output to include a list of
	      token names in order by their token numbers;  this is defined in
	      the  array  yytname.  Also generated are #defines for YYNTOKENS,

	      Don't put any #line preprocessor commands in  the	 parser	 file.
	      Ordinarily bison puts them in the parser file so that the C com‐
	      piler 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.

	      Do  not generate the parser code into the output;	 generate only
	      declarations.  The generated file will have only con‐
	      stant  declarations.   In addition, a name.act file is generated
	      containing a switch statement body containing all the translated

       -o outfile
	      Specify the name outfile for the parser file.

	      The  other  output  files' names are constructed from outfile as
	      described under the -v and -d switches.

       -p prefix
	      Rename the external symbols used in  the	parser	so  that  they
	      start  with  prefix  instead of yy.  The precise list of symbols
	      renamed is yyparse, yylex, yyerror, yylval, yychar, and yydebug.

	      For example, if you use -p c, the names become cparse, clex, and
	      so on.

	      Output  a	 definition of the macro YYDEBUG into the parser file,
	      so that the debugging facilities are compiled.

	      Write an extra output file containing  verbose  descriptions  of
	      the  parser  states and what is done for each type of look-ahead
	      token in that state.

	      This file also describes all the conflicts, both those  resolved
	      by operator precedence and the unresolved ones.

	      The file's name is made by removing .tab.c or .c from the parser
	      output file name, and adding .output instead.

	      Therefore, if the input file is foo.y, then the parser  file  is
	      called by default.  As a consequence, the verbose out‐
	      put file is called foo.output.

	      Print the version number of bison and exit.

       --help Print a summary of the options to bison and exit.

	      Equivalent to -o;	 the  parser  output  file  is	called,	and the other outputs are called y.output and
	      The purpose of this switch is to imitate yacc's output file name
	      conventions.   Thus,  the	 following shell script can substitute
	      for yacc:

	      bison -y $*

       /usr/local/lib/bison.simple   simple parser
       /usr/local/lib/bison.hairy    complicated parser

	      If  this	is  set,  it  specifies	 the  location	in  which  the
	      bison.simple parser can be found.

	      If  this	is  set,  it  specifies	 the  location	in  which  the
	      bison.hairy parser can be found.

       The Bison Reference Manual, included as the file bison.texinfo  in  the
       bison source distribution.

       Self explanatory.

				     local			      BISON(1)

List of man pages available for Ultrix

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net