(Debugging): Remove YYSTDERR; it's no longer defined or used.

Also, s/cstdio.h/cstdio/.
This commit is contained in:
Paul Eggert
2002-01-05 01:25:38 +00:00
parent 1109455ce9
commit e2742e46ba

View File

@@ -4950,13 +4950,13 @@ Summary}). We suggest that you always define @code{YYDEBUG} so that
debugging is always possible. debugging is always possible.
The trace facility outputs messages with macro calls of the form The trace facility outputs messages with macro calls of the form
@code{YYFPRINTF (YYSTDERR, @var{format}, @var{args})} where @code{YYFPRINTF (stderr, @var{format}, @var{args})} where
@var{format} and @var{args} are the usual @code{printf} format and @var{format} and @var{args} are the usual @code{printf} format and
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
define @code{YYFPRINTF}, @code{<stdio.h>} is automatically included define @code{YYFPRINTF}, @code{<stdio.h>} is automatically included
and the macros are defined to @code{fprintf} and @code{stderr}. In and @code{YYPRINTF} is defined to @code{fprintf}. In the same
the same situation, C++ parsers include @code{<cstdio.h>} instead, and situation, C++ parsers include @code{<cstdio>} and use
use @code{std::fprintf} and @code{std::stderr}. @code{std::fprintf} instead.
Once you have compiled the program with trace facilities, the way to Once you have compiled the program with trace facilities, the way to
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}.