bison++ - generate a parser in c or c++.

bison++ [-dltvyVu] [-b file-prefix] [-p name-prefix] [-o outfile] [-h headerfile] [-S skeleton] [-H header-skeleton] [--debug] [--defines] [--fixed-output-files] [--no-lines] [--verbose] [--version] [--yacc] [--usage] [--help] [--file-prefix=prefix] [--name-prefix=prefix] [--skeleton=skeletonfile] [--headerskeleton=headerskeletonfile] [--output=outfile] [--header-name=header] grammar-file

Generate a parser. Based on bison version 1.19. See bison(1) for details of main functionality. Only changes are reported here.

You now generate a C++ class if you are compiling with a C++ compiler. The generated header is far more rich than before, and is made from a skeleton-header. The code skeleton is also richer, and the generated code is less important compared to the skeletons. It permit you to modify much things only by changing the two skeletons.

In plain C, the bison++ is compatible with standard bison.

\fB\-\-name\-prefix=\fP\fIprefix\fP

\fB\-p\fP \fIprefix\fP

Set prefix of names of yylex,yyerror. keeped for compatibility, but you should prefer %define LEX newname, and similar.

\fB\-\-skeleton=\fP\fIskeleton\fP

\fB\-S\fP \fIskeleton\fP

Set filename of code skeleton. Default is bison.cc.

\fB\-\-headerskeleton=\fP\fIheader\-skeleton\fP

\fB\-H\fP \fIheader\-skeleton\fP

Set filename of header skeleton. Default is bison.h.

\fB\-\-header\-name=\fP\fIheader\fP

\fB\-h\fP \fIheader\fP

Set filename of header skeleton. Default is y.tab.h, or prefix.h if option -b is used or c_basename.h if -o is used. .c, .cc, .C, .cpp, .cxx options for output files are replaced by .h for header name.

These are new declarations to put in the declaration section :

\fB%name\fP \fIparser_name\fP

Declare the name of this parser. User for C++ class name, and to render many names unique. default is parse. Must be given before %union and %define, or never.

\fB%define\fP \fIdefine_name\fP \fIcontent\.\.\.\fP

Declare a macro symbol in header and code. The name of the symbol is YY_'parser_name'_'define_name'. The content if given after, as with #define. Newline can be escaped as with #define. Many symbols are proposed for customisation.

\fB%union\fP

as with bison generate a union for semantic type. The difference is that the union is named yy_'parser_name'_stype.

\fB%pure_parser\fP

As with bison in C. In C++ generate a parser where yylval, and yylloc (if needed) are passed as parameter to yylex, and where some instance variable are local to yyparse (like yydebug...). Not very useful, since you can create multiple instances for reentering another parser.

\fB%header{\fP

Like %{, but include this text both in the header, and in the code. End with %}. When put in declaration section, the text is added before the definitions. It can be put in the last section so that the text is added after all definition in the header, and in the last section at the current position in the code.

Note that the order of these declaration is important, since they are translated into preprocessor sympols, typedef or code depending on their type. For example use %name before any %define, since the name is needed to compose the name of the define symbols. Order of %header and %union is important, since type may be undefined.

These are the symbols you can define with %define in declaration section, or that are already defined. Remind that they are replaced by a preprocessor #define YY_'parser_name'_'name.

\fBBISON\fP

defined to 1 in the code. used for conditional code. Don't redefine it.

\fBh_included\fP

defined in the code, and in the header. used for include anti-reload. Don't redefine it.

\fBCOMPATIBILITY\fP

Indicate if obsoleted defines are to be used and produced. If defined to 0, indicate no compatibility needed, else if defined to non-0, generate it. If it is undefined, default is to be compatible if classes are not used.

\fBUSE_GOTO\fP

Indicates (if defined as 1) that goto are to be used (for backward compatibility) in the parser function. By default goto are replaced with a switch construction, to avoid problems with some compiler that don't support goto and destructor in the same function block. If COMPATIBILITY is 1, and USE_GOTO is not defined, then USE_GOTO is defined to 1, to be compatible with older bison.

\fBUSE_CONST_TOKEN\fP

Indicate (if defined as 1) that static const int are to be used in C++, for token IDs. By default an enum is used to define the token IDs instead of const.

\fBENUM_TOKEN\fP

When enum are used instead of static const int for token IDs, this symbol define the name of the enum type. Defined to yy_'parser_name'_enum_token by default.

\fBPURE\fP

Indicate that %pure_parser is asked... Don't redefine it.

\fBLSP_NEEDED\fP

if defined indicate that @ construct is used, so LLOC stack is needed. Can be defined to force use of location stack.

\fBDEBUG\fP

if defined to non-0 activate debugging code. See YYDEBUG in bison.

\fBERROR_VERBOSE\fP

if defined activate dump parser stack when error append.

\fBSTYPE\fP

the type of the semantic value of token. defined by %union. default is int. See YYSTYPE in bison. Don't redefine it, if you use a %union.

\fBLTYPE\fP

The token location type. If needed default is yyltype. See YYLTYPE in bison. default yyltype is a typedef and struct defined as in old bison.

\fBLLOC\fP

The token location variable name. If needed, default is yylloc. See yylloc in bison.

\fBLVAL\fP

The token semantic value variable name. Default yylval. See yylval in bison.

\fBCHAR\fP

The lookahead token value variable name. Default yychar. See yychar in bison.

\fBLEX\fP

The scanner function name. Default yylex. See yylex in bison.

\fBPARSE\fP

The parser function name. Default yyparse. See yyparse in bison.

\fBPARSE_PARAM\fP

The parser function parameters declaration. Default void in C++ or ANSIC, nothing if old C. In ANSIC and C++ contain the prototype. In old-C comtaim just the list of parameters name. Don't allows default value.

\fBPARSE_PARAM_DEF\fP

The parser function parameters definition, for old style C. Default nothing. For example to use an int parameter called x, PARSE_PARAM is x, and PARSE_PARAM_DEF is int x;. In ANSIC or C++ it is unuseful and ignored.

\fBERROR\fP

The error function name. Default yyerror. See yyerror in bison.

\fBNERRS\fP

The error count name. Default yynerrs. See yynerrs in bison.

\fBDEBUG_FLAG\fP

The runtime debug flag. Default yydebug. See yydebug in bison.

These are only used if class is generated.

\fBCLASS\fP

The class name. default is the parser name.

\fBINHERIT\fP

The inheritance list. Don't forget the : before, if not empty list.

\fBMEMBERS\fP

List of members to add to the class definition, before ending it.

\fBLEX_BODY\fP

The scanner member function boby. May be defined to =0 for pure function, or to an inline body.

\fBERROR_BODY\fP

The error member function boby. May be defined to =0 for pure function, or to an inline body.

\fBCONSTRUCTOR_PARAM\fP

List of parameters of the constructor. Dont allows default value.

\fBCONSTRUCTOR_INIT\fP

List of initialisation befor constructor call. If not empty dont't forget the : before list of initialisation.

\fBCONSTRUCTOR_CODE\fP

Code added after internal initialisation in constructor.

if you use new features, the folowing symbols should not be used, though they are proposed. The symbol COMPATIBILITY control their disponibility. Incoherence may arise if they are defined simultaneously with the new symbol.

\fBYYLTYPE\fP

prefer %define LTYPE.

\fBYYSTYPE\fP

prefer %define STYPE.

\fBYYDEBUG\fP

prefer %define DEBUG.

\fBYYERROR_VERBOSE\fP

prefer %define ERROR_VERBOSE.

\fBYYLSP_NEEDED\fP

prefer %define LSP_NEEDED.

\fByystype\fP

Now a preprocessor symbol instead of a typedef. prefer yy_'parser_name'_stype.

These symbols are kept, and cannot be defined elsewhere, since they control private parameters of the generated parser, or are actually unused. You can #define them to the value you need, or indirectly to the name of a %define generated symbol if you want to be clean.

\fBYYINITDEPTH\fP

initial stack depth.

\fBYYMAXDEPTH\fP

stack overflow limit depth.

\fByyoverflow\fP

instead of expand with alloca, realloc manualy or raise error.

\fBYY_USE_CLASS\fP

indicate that class will be produced. Default if C++.

To simplify the notation, we note %SYMBOLNAME the preprocessor symbol generated with a %define of this name. In fact see the use of %define for it's real name.

Note that there is sometime symbols that differ from only an underscore _, like yywrap and yy_wrap. They are much different. In this case yy_wrap() is a virtual member function, and yywrap() is a macro.

General Class declaration

Default Class declaration

Should replace bison, because it generate a far more customisable parser, still beeing compatible.

You should always use the header facility.

Use it with flex++ (same author).

This man page has been produced through a parser made in C++ with this version of bison and our version of flex++ (same author).

\fBbison\.cc\fP

main skeleton.

\fBbison\.h\fP

header skeleton.

\fBbison\.hairy\fP

old main skeleton for semantic parser. Not adapted to this version. Kept for future works.

bison(1), bison.info (use texinfo), flex++(1).

Tell us more !

The %semantic_parser is no more supported. If you want to use it, adapt the skeletons, and maybe bison++ generator itself. The reason is that it seems unused, unuseful, not documented, and too complex for us to support. tell us if you use, need, or understand it.

Header is not included in the parser code. Change made in the generated header are not used in the parser code, even if you include it volontarily, since it is guarded against re-include. So don't modify it.

For the same reasons, if you modify the header skeleton, or the code skeleton, report the changes in the other skeleton if applicable. If not done, incoherent declarations may lead to unpredictable result.

Use of defines for YYLTYPE, YYSTYPE, YYDEBUG is supported for backward compatibility in C, but should not be used with new features, as %defines or C++ classes. You can define them, and use them as with old bison in C only.

Parameters are richer than before, and nothing is removed. POSIX compliance can be enforced by not using extensions. If you want to forbide them, there is a good job !

tell us !

Support semantic parser. Is it really used ?

POSIX compliance. is'nt it good now ?

Use lex and yacc (flex/bison) to generate the scanner/parser. It would be comfortable for futur works, though very complicated. Who feel it good ?

iostream : this is a great demand. this work will be done as soon as possible. The virtual members permit such work still easily.

With this install the executable is named bison++. rename it bison if you want, because it could replace bison.

Alain Coe:tmeur (coetmeur@icdc.fr), R&D department (RDT) , Informatique-CDC, France.

The words 'author', and 'us' mean the author and colleages, not GNU. We don't have contacted GNU about this, nowaday. If you're in GNU, we are ready to propose it to you, and you may tell us what you think about.

Based on GNU version 1.21 of bison. Modified by the author.