specifying a C++ template class parse-param

2006-12-13 Thread galexander2
I'm using Bison to generate a parser that I compile with g++. I'm using using the default Bison skeleton, not the Bison C++ skeleton. I would like to pass a reference to a C++ template class, such as A& a where T is the template parameter, to yyparse. I specify %parse-param {A& a} in my Biso

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > Fixed it. Good thinking Joel :) Great. > So, should I try any other configurations? Nah, thanks. I think it's clear that we need Autoconf 2.61, which requires a newer M4. However, I see no evidence that Bison users (who shouldn't need to run Autoconf)

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 05:11:37PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > $ m4 --version > > GNU M4 1.4.8 > > [EMAIL PROTECTED] ~/cvs/bison/original/bison > > $ autoconf --version > > autoconf (GNU Autoconf) 2.61 > > > > I still get the bootstrap error > > > >

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > $ m4 --version > GNU M4 1.4.8 > [EMAIL PROTECTED] ~/cvs/bison/original/bison > $ autoconf --version > autoconf (GNU Autoconf) 2.61 > > I still get the bootstrap error > > configure.ac:111: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > m4/get

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 04:57:33PM -0500, Bob Rossi wrote: > On Wed, Dec 13, 2006 at 04:23:29PM -0500, Joel E. Denny wrote: > > On Wed, 13 Dec 2006, Joel E. Denny wrote: > > > > > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > > > > > With a fresh check out, and autoconf 2.6.1 on my path, after runn

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 04:23:29PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Joel E. Denny wrote: > > > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > > > With a fresh check out, and autoconf 2.6.1 on my path, after running > > > ./bootstrap.sh > > > > You mean "./bootstrap", right? > > >

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 04:03:31PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > With a fresh check out, and autoconf 2.6.1 on my path, after running > > ./bootstrap.sh > > You mean "./bootstrap", right? Yes. > I just tried a fresh checkout. I'm not having any troub

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > With a fresh check out, and autoconf 2.6.1 on my path, after running > > ./bootstrap.sh > > You mean "./bootstrap", right? > > I just tried a fresh checkout. I'm not having any trouble. > > > configure.ac:

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > With a fresh check out, and autoconf 2.6.1 on my path, after running > ./bootstrap.sh You mean "./bootstrap", right? I just tried a fresh checkout. I'm not having any trouble. > configure.ac:111: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 03:28:29PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > > 2.61 has some corrections regarding strange test case titles, which my > > > recent patches add to Bison. I can't promise it'll fix your problem, but > > > we should start there. > >

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > > 2.61 has some corrections regarding strange test case titles, which my > > recent patches add to Bison. I can't promise it'll fix your problem, but > > we should start there. > > I need to upgrade? If so, you should put an AC_REQUIRE line, for 2.61. Y

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 03:21:25PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > On Wed, Dec 13, 2006 at 03:13:30PM -0500, Joel E. Denny wrote: > > > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > > > > > make maintainer-check recently broke in CVS. > > > > > > > > $ mak

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > On Wed, Dec 13, 2006 at 03:13:30PM -0500, Joel E. Denny wrote: > > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > > > make maintainer-check recently broke in CVS. > > > > > > $ make maintainer-check > > > cd tests && make maintainer-check > > > make[1]: Ente

Re: make maintainer-check broke

2006-12-13 Thread Bob Rossi
On Wed, Dec 13, 2006 at 03:13:30PM -0500, Joel E. Denny wrote: > On Wed, 13 Dec 2006, Bob Rossi wrote: > > > make maintainer-check recently broke in CVS. > > > > $ make maintainer-check > > cd tests && make maintainer-check > > make[1]: Entering directory `/home/bob/cvs/bison/round2/bison/tests'

Re: make maintainer-check broke

2006-12-13 Thread Joel E. Denny
On Wed, 13 Dec 2006, Bob Rossi wrote: > make maintainer-check recently broke in CVS. > > $ make maintainer-check > cd tests && make maintainer-check > make[1]: Entering directory `/home/bob/cvs/bison/round2/bison/tests' > ./testsuite POSIXLY_CORRECT=1 _POSIX2_VERSION=200112 > c++: no input files

make maintainer-check broke

2006-12-13 Thread Bob Rossi
Hi, make maintainer-check recently broke in CVS. $ make maintainer-check cd tests && make maintainer-check make[1]: Entering directory `/home/bob/cvs/bison/round2/bison/tests' ./testsuite POSIXLY_CORRECT=1 _POSIX2_VERSION=200112 c++: no input files ./testsuite: line 657: syntax error near unexpe

Re: bison and C++

2006-12-13 Thread Hans Aberg
On 13 Dec 2006, at 11:33, Evan Lavelle wrote: Once upon the time, Bison had an informal support for the C-parser to be compiled as C++, but this was dropped, being too difficult to maintain. Instead, a separate C++ skeleton was developed. So, for C++, it is best to use the C++ skeleton file.

Re: bison and C++

2006-12-13 Thread Evan Lavelle
Hans Aberg wrote: Once upon the time, Bison had an informal support for the C-parser to be compiled as C++, but this was dropped, being too difficult to maintain. Instead, a separate C++ skeleton was developed. So, for C++, it is best to use the C++ skeleton file. I have a lot of C++ code i