Re: Bison FAQ C++ entry is obsolete?

[Paul Eggert]

address@hidden writes:

>>> few protofiles need update,
>> Sorry, what's a "protofile"?
> the .h files, see the tool cextract

So I take it that some of the prototypes in the .h files are
incorrect?  Can you give me an example?  Sorry, I'm still lost.  (I
don't use cextract.)

> the Q5 in the FAQ on C++ can mention Bison C++ support
> but it is still in development.
> struct obstack solved_conflicts_obstack; in conflicts.c can be a static.

Thanks for reporting these; they are fixed in the patch below.

> the `splice (\\[ \f\t\v]*\n)*' in scan-gram.l really correct?
> it does allow for a c comment like /^f* comment *^v/ in parser
> specifications.

Sorry, I don't see how such a comment would be allowed.
Can you give a test case?

Anyway, I installed this:

2006-03-08  Paul Eggert  <address@hidden>

        Fix some nits reported by twlevo.
        * doc/FAQ: Remove ancient Y2K FAQ, replacing it with "secure"
        and "POSIX".  Use more-modern syntax for URLs.  Mention C++
        and ask for Java.  Don't hardwire OS version numbers.  Add
        copyright notice.
        * m4/.cvsignore: Add unistd_h.m4, for latest gnulib.
        * src/conflicts.c (solved_conflicts_obstack): Now static.

Index: doc/FAQ
===================================================================
RCS file: /cvsroot/bison/bison/doc/FAQ,v
retrieving revision 1.4
diff -p -u -r1.4 FAQ
--- doc/FAQ     30 Nov 2002 09:25:06 -0000      1.4
+++ doc/FAQ     8 Mar 2006 19:44:47 -0000
@@ -2,13 +2,12 @@ Frequently Asked Questions about Bison:
 
 ----------------------------------------------------------------------
 
-Q1.  Is Bison Y2K compliant?
+Q1.  Is Bison secure?  Does it conform to POSIX?
 
-A1.  If you're looking for a guarantee or certification, I can't
-     provide it.  With a little thought you can answer this one for
-     yourself, though.  (Hint: does a parser generator rely on the
-     date or time for anything?)  If you're still confused, see
-     http://www.gnu.org/software/year2000.html for more information.
+A1.  If you're looking for a guarantee or certification, we don't
+     provide it.  However, Bison is intended to be a reliable program
+     that conforms to the POSIX specification for Yacc.  If you run
+     into problems, please send us a bug report.
 
 ----------------------------------------------------------------------
 
@@ -20,7 +19,7 @@ A2.  Like most GNU packages with interna
      in the "po" subdirectory, it indicates that your system's
      internationalization support is lacking.  You can re-configure
      Bison with "--disable-nls" to turn off this support, or you can
-     install GNU gettext from ftp://ftp.gnu.org/gnu/gettext/ and
+     install GNU gettext from <ftp://ftp.gnu.org/gnu/gettext/> and
      re-configure Bison.  See the file "ABOUT-NLS" for more
      information.
 
@@ -44,7 +43,7 @@ A3.  First, read the fine manual which c
 Q4.  I found a bug.  What should I include in the bug report?
 
 A4.  Before you send a bug report, make sure you are using the latest
-     version.  Check ftp://ftp.gnu.org/pub/gnu/bison/ or one of its
+     version.  Check <ftp://ftp.gnu.org/pub/gnu/bison/> or one of its
      mirrors.  Be sure to include the version number in your bug
      report.  If the bug is present in the latest version but not in a
      previous version, try to determine the most recent version which
@@ -72,14 +71,11 @@ A4.  Before you send a bug report, make 
 
 ----------------------------------------------------------------------
 
-Q5.  Will Bison ever have C++ support?
+Q5.  Will Bison ever have C++ support?  How about Java or
+     <insert your favorite language here>?
 
-A5.  Yes, it's in the works.  Things are very chaotic right now, but
-     what little information floats around is posted to the bug-bison
-     mailing list.  If you're interested in testing C++ support when
-     it becomes available, please consider subscribing to the list,
-     especially if you are willing to beta test other releases as
-     well.
+A5.  C++ support is there now, and is documented in the manual.
+     We'd love to add other languages; contributions are welcome.
 
 ----------------------------------------------------------------------
 
@@ -94,16 +90,33 @@ A6.  It's not terribly involved.  Basica
      tested.  If no one tests, development is essentially halted.
 
      Beta testers are particularly needed for operating systems to
-     which I do not have access.  I currently have easy access to
-     Linux (x86 glibc 2.1), Solaris (SPARC) 2.6 and 2.7, and HP-UX
-     10.20.  Reports about other operating systems are especially
-     welcome.
+     which the developers do not have easy access.  They currently
+     have easy access to recent GNU/Linux and Solaris versions.
+     Reports about other operating systems are especially welcome.
 
 ----------------------------------------------------------------------
 
 Q7.  How do I join the help-bison and bug-bison mailing lists?
 
-A7.  See http://www.gnu.org/ (the section about "GNU mailing lists")
-     for more information.
+A7.  See <http://lists.gnu.org/>.
 
 ----------------------------------------------------------------------
+
+Copyright (C) 1999, 2002, 2006 Free Software Foundation, Inc.
+
+This file is part of Bison, the GNU Compiler Compiler.
+
+Bison is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+Bison is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with autoconf; see the file COPYING.  If not, write to
+the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
+Boston, MA 02110-1301, USA.
Index: m4/.cvsignore
===================================================================
RCS file: /cvsroot/bison/bison/m4/.cvsignore,v
retrieving revision 1.15
diff -p -u -r1.15 .cvsignore
--- m4/.cvsignore       2 Oct 2005 18:49:15 -0000       1.15
+++ m4/.cvsignore       8 Mar 2006 19:44:47 -0000
@@ -32,6 +32,7 @@ strtol.m4
 strtoul.m4
 strverscmp.m4
 unistd-safer.m4
+unistd_h.m4
 unlocked-io.m4
 xalloc.m4
 xstrndup.m4
Index: src/conflicts.c
===================================================================
RCS file: /cvsroot/bison/bison/src/conflicts.c,v
retrieving revision 1.114
diff -p -u -r1.114 conflicts.c
--- src/conflicts.c     21 Jan 2006 04:35:09 -0000      1.114
+++ src/conflicts.c     8 Mar 2006 19:44:47 -0000
@@ -40,7 +40,7 @@
 int expected_sr_conflicts = -1;
 int expected_rr_conflicts = -1;
 static char *conflicts;
-struct obstack solved_conflicts_obstack;
+static struct obstack solved_conflicts_obstack;
 
 static bitset shift_set;
 static bitset look_ahead_set;