Bug#689700: *** GMX Spamverdacht *** Re: bison 2.6.2 generates incompatible header file

2012-10-19 Thread Frank Heckenbach
Akim Demaille wrote: Indeed, if you want both to be in the same namespace, %define api.prefix should do what you want. Note that the C++ output supports %define namespace, in which the generated code is put. Thanks, seems like we have several viable options here. (Though I'd have to check

Bug#689700: *** GMX Spamverdacht *** Re: bison 2.6.2 generates incompatible header file

2012-10-18 Thread Frank Heckenbach
Bill Allombert wrote: A way to fix the problem could be to add #ifdef __cplusplus extern C { #endif ... #ifdef __cplusplus } #endif in the generated parse.tab.h. This is not correct for people who do not want this guy to be in extern C. I agree, but I

Bug#689700: *** GMX Spamverdacht *** Re: bison 2.6.2 generates incompatible header file

2012-10-18 Thread Bill Allombert
On Thu, Oct 18, 2012 at 06:52:41PM +0200, Frank Heckenbach wrote: Bill Allombert wrote: We do compile our Bison output with g++ (yes, we should probably use the C++ skeleton, but we haven't gotten around to it yet), and we don't use extern C -- in fact we use two different parsers in one