Re: problems compiling groff with gcc-3.0.3

[Hans Aberg]

At 01:55 +0100 2002/01/26, Werner LEMBERG wrote:
>> Yes, Bison is the culprit, there is no debating about that.  Sorry
>> Werner.  I will nonetheless ask you to adjust your sources to our
>> bug.  I don't plan 1.33 immediately: I'll first wait for other
>> issues to be reported.  Is that an actual problem?
>
>Not really.  I will add something to the PROBLEMS file that people
>should avoid version bison versions 1.30h-1.32.  Both yacc will do
>quite fine also.

I did not follow this closely enough to see whether what Akim here calls a
"bug" really is a bug:

If people, while compiling under C++, experience a problem with getting
std::size_t instead of the old ::size_t, then the best option is to use
latest Bison and update the sources, as this is how C++ code is moving
anyway:

If the C++ compiler is up-to-date, one can try to flip in a "using
namespace std;" somewhere appropriate. More ambitiously, one would use
"using std::size_t;" instead or even replace size_t with std::size_t (and
the same for other conflicting names). This way, one makes one code
up-to-date relative the C++ standard.

Only if this does not work or is possible, one might try older versions of
Bison (but then one might experience other bugs).

  Hans Aberg