> >>> "GDA" == Geoffrey D Alexander <[EMAIL PROTECTED]> writes:
>
> > However, I did notice a slowdown of 5 to 20 percent in the C++ parser.
> > Also, the C++ parser shows an increase of 10 to 15 percent in the number
> > of memory allocation as reported by valgrind.
>
> > Is this a known probl
>>> "GDA" == Geoffrey D Alexander <[EMAIL PROTECTED]> writes:
> However, I did notice a slowdown of 5 to 20 percent in the C++ parser.
> Also, the C++ parser shows an increase of 10 to 15 percent in the number
> of memory allocation as reported by valgrind.
> Is this a known problem? Are the
On 2 Feb 2007, at 09:53, Geoffrey D Alexander wrote:
I have a C parser (using the C skeleton) that contains C++ code
that I'm
compiling with g++. The parser works fine. But a previous thread
titled
"bison and C++" from December 2006 said that compiling C parsers
with a
C++ compiler is no
I have a C parser (using the C skeleton) that contains C++ code that I'm
compiling with g++. The parser works fine. But a previous thread titled
"bison and C++" from December 2006 said that compiling C parsers with a
C++ compiler is no longer support. So, I converted my compiler to use
the C++ sk
