From e2742e46ba337f2717a6cd9cfde62bace920e468 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 5 Jan 2002 01:25:38 +0000 Subject: [PATCH] (Debugging): Remove YYSTDERR; it's no longer defined or used. Also, s/cstdio.h/cstdio/. --- doc/bison.texinfo | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/bison.texinfo b/doc/bison.texinfo index f4360cd3..029e2490 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -4950,13 +4950,13 @@ Summary}). We suggest that 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}. -- 2.45.2