[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: yet another C++ implementation bug to work around in Bison
From: |
Paul Eggert |
Subject: |
Re: yet another C++ implementation bug to work around in Bison |
Date: |
Mon, 06 Feb 2006 00:01:18 -0800 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) |
Hans Aberg <address@hidden> writes:
> 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.
It is not needed. The map stuff is used only by the user-code example
in the Bison manual, which is tested by compiling it. Please see the
Bison source code for details.
> So, if not, the installation of Bison need not check it, but only as
> a part of a "make check".
That would make sense, yes, but it will require that someone (not me!)
actually implement such a change, and not just talk about it.
> It is also strange if a C++ compiler, at
> this late date, cannot handle std::map properly.
I don't find it strange at all, and I'm not a bit surprised by it.