From: Paul Eggert Date: Sat, 5 Jan 2002 01:18:26 +0000 (+0000) Subject: (Debugging): Remove YYSTDERR; it's no longer defined or used. X-Git-Tag: BISON-1_30j~12 X-Git-Url: https://git.saurik.com/bison.git/commitdiff_plain/f36280e16e244d553453d92097461435d3ac5112?ds=sidebyside (Debugging): Remove YYSTDERR; it's no longer defined or used. Also, s/cstdio.h/cstdio/. --- diff --git a/doc/bison.texinfo b/doc/bison.texinfo index e9e37701..2e5fefa7 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -4935,13 +4935,13 @@ Alternatively, use the @samp{-t} option when you run Bison you always define @code{YYDEBUG} so that debugging is always possible. 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 arguments. If you define @code{YYDEBUG} to a nonzero value but do not define @code{YYFPRINTF}, @code{} is automatically included -and the macros are defined to @code{fprintf} and @code{stderr}. In -the same situation, C++ parsers include @code{} instead, and -use @code{std::fprintf} and @code{std::stderr}. +and @code{YYPRINTF} is defined to @code{fprintf}. In the same +situation, C++ parsers include @code{} and use +@code{std::fprintf} instead. 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}.