From e4e1a4dcb41f3c2b47ffb7668eac97900b1498f9 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 14 Feb 2002 20:26:54 +0000 Subject: [PATCH 1/1] (Bison Parser, Debugging): Remove special mention of C++, as it's treated like C now. --- doc/bison.texinfo | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/bison.texinfo b/doc/bison.texinfo index 029e2490..7c0b3454 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -707,8 +707,7 @@ In some cases the Bison parser file includes system headers, and in those cases your code should respect the identifiers reserved by those headers. On some non-@sc{gnu} hosts, @code{}, @code{}, and @code{} are included as needed to -declare memory allocators and related types. In the same situation, -C++ parsers may include @code{} and @code{} instead. +declare memory allocators and related types. Other system headers may be included if you define @code{YYDEBUG} to a nonzero value (@pxref{Debugging, ,Debugging Your Parser}). @@ -4954,9 +4953,7 @@ The trace facility outputs messages with macro calls of the form @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 @code{YYPRINTF} is defined to @code{fprintf}. In the same -situation, C++ parsers include @code{} and use -@code{std::fprintf} instead. +and @code{YYPRINTF} is defined to @code{fprintf}. 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.47.2