693 |
@xref{Interface, ,Parser C-Language Interface}. |
@xref{Interface, ,Parser C-Language Interface}. |
694 |
|
|
695 |
Aside from the token type names and the symbols in the actions you |
Aside from the token type names and the symbols in the actions you |
696 |
write, all variable and function names used in the Bison parser file |
write, all symbols defined in the Bison parser file itself |
697 |
begin with @samp{yy} or @samp{YY}. This includes interface functions |
begin with @samp{yy} or @samp{YY}. This includes interface functions |
698 |
such as the lexical analyzer function @code{yylex}, the error reporting |
such as the lexical analyzer function @code{yylex}, the error reporting |
699 |
function @code{yyerror} and the parser function @code{yyparse} itself. |
function @code{yyerror} and the parser function @code{yyparse} itself. |
702 |
or @samp{YY} in the Bison grammar file except for the ones defined in |
or @samp{YY} in the Bison grammar file except for the ones defined in |
703 |
this manual. |
this manual. |
704 |
|
|
705 |
|
In some cases the Bison parser file includes system headers, and in |
706 |
|
those cases your code should respect the identifiers reserved by those |
707 |
|
headers. On some non-@sc{gnu} hosts, @code{<alloca.h>}, |
708 |
|
@code{<stddef.h>}, and @code{<stdlib.h>} are included as needed to |
709 |
|
declare memory allocators and related types. On all hosts, |
710 |
|
@code{<stdio.h>} is included if you define @code{YYDEBUG} |
711 |
|
(@pxref{Debugging, ,Debugging Your Parser}). |
712 |
|
|
713 |
@node Stages |
@node Stages |
714 |
@section Stages in Using Bison |
@section Stages in Using Bison |
715 |
@cindex stages in using Bison |
@cindex stages in using Bison |