707 |
those cases your code should respect the identifiers reserved by those |
those cases your code should respect the identifiers reserved by those |
708 |
headers. On some non-@sc{gnu} hosts, @code{<alloca.h>}, |
headers. On some non-@sc{gnu} hosts, @code{<alloca.h>}, |
709 |
@code{<stddef.h>}, and @code{<stdlib.h>} are included as needed to |
@code{<stddef.h>}, and @code{<stdlib.h>} are included as needed to |
710 |
declare memory allocators and related types. In the same situation, |
declare memory allocators and related types. |
|
C++ parsers may include @code{<cstddef>} and @code{<cstdlib>} instead. |
|
711 |
Other system headers may be included if you define @code{YYDEBUG} to a |
Other system headers may be included if you define @code{YYDEBUG} to a |
712 |
nonzero value (@pxref{Debugging, ,Debugging Your Parser}). |
nonzero value (@pxref{Debugging, ,Debugging Your Parser}). |
713 |
|
|
4953 |
@var{format} and @var{args} are the usual @code{printf} format and |
@var{format} and @var{args} are the usual @code{printf} format and |
4954 |
arguments. If you define @code{YYDEBUG} to a nonzero value but do not |
arguments. If you define @code{YYDEBUG} to a nonzero value but do not |
4955 |
define @code{YYFPRINTF}, @code{<stdio.h>} is automatically included |
define @code{YYFPRINTF}, @code{<stdio.h>} is automatically included |
4956 |
and @code{YYPRINTF} is defined to @code{fprintf}. In the same |
and @code{YYPRINTF} is defined to @code{fprintf}. |
|
situation, C++ parsers include @code{<cstdio>} and use |
|
|
@code{std::fprintf} instead. |
|
4957 |
|
|
4958 |
Once you have compiled the program with trace facilities, the way to |
Once you have compiled the program with trace facilities, the way to |
4959 |
request a trace is to store a nonzero value in the variable @code{yydebug}. |
request a trace is to store a nonzero value in the variable @code{yydebug}. |