Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Kitty Hooch

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 55 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       bison  [  -b file-prefix ] [ --file-prefix=file-prefix ] [
       -d ] [ --defines=defines-file ] [ -g  ]  [  --graph=graph-
       file ] [ -k ] [ --token-table ] [ -l ] [ --no-lines ] [ -n
       ] [ --no-parser ] [ -o outfile ] [ --output-file=outfile ]
       [  -p prefix ] [ --name-prefix=prefix ] [ -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.
       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  gener­
       ated  parser  in  a  file  named parse.tab.cxx, instead of
       yacc's y.tab.c or old Bison versions 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 authoritative.

       Bison supports both traditional single-letter options  and
       mnemonic  long  option names.  Long option names are indi­
       cated 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 defini­
              tions for the token type names defined in the gram­
              mar 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.

              foo.y , the VCG output file will be foo.vcg.

              The  behaviour  of  --graph  is  the  same  than -g
              option. The only  difference  is  that  it  has  an
              optionnal  argument which is the name of the output
              graph filename.

              This switch causes the name.tab.c output to include
              a  list of token names in order by their token num­
              bers;  this is defined in the array yytname.   Also
              generated  are #defines for YYNTOKENS, YYNNTS, YYN­
              RULES, and YYNSTATES.

              Don't put any #line preprocessor  commands  in  the
              parser  file.   Ordinarily  bison  puts them in the
              parser file so that the C  compiler  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 inde­
              pendent source file in its own right.

              Do not generate the parser code  into  the  output;
              generate    only   declarations.    The   generated
              name.tab.c file will have  only  constant  declara­
              tions.   In  addition, a name.act file is generated
              containing a switch statement body  containing  all
              the translated actions.

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

              solved ones.

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

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

              Print the version number of bison and exit.

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

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

              bison -y $*


       /usr/local/share/bison/bison.simple     simple parser
       /usr/local/share/bison/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.

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.12 Seconds