Re: yet another C++ implementation bug to work around in Bison

[Hans Aberg]

On 3 Feb 2006, at 01:01, Paul Eggert wrote:

> One possible, more drastic fix that comes to mind is that we should
> not use C++ at all, as part of our normal build procedure.  It often
> causes build failures, and it's not really needed for Bison, so
> perhaps the C++ stuff should all get moved to "make check".

I do not see why std::map would be needed as a part of the generated  
Bison parser, i.e., if the user code does not include it. So, if not,  
the installation of Bison need not check it, but only as a part of a  
"make check". It is also strange if a C++ compiler, at this late  
date, cannot handle std::map properly.

  Hans Aberg