(Bison Parser, Debugging): Remove special mention of C++, as it's

treated like C now.

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 029e249066436b3a1cbcea3551f4d286eabcb9fe..7c0b3454e1c99b1016d964a729611a226cd96da4 100644 (file)
--- 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{<alloca.h>},
 @code{<stddef.h>}, and @code{<stdlib.h>} are included as needed to
-declare memory allocators and related types.  In the same situation,
-C++ parsers may include @code{<cstddef>} and @code{<cstdlib>} 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{<stdio.h>} is automatically included
-and @code{YYPRINTF} is defined to @code{fprintf}.  In the same
-situation, C++ parsers include @code{<cstdio>} 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}.