[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison 1.30f

From: Paul Eggert
Subject: Re: Bison 1.30f
Date: Mon, 10 Dec 2001 13:12:54 -0800 (PST)

> Date: Mon, 10 Dec 2001 19:50:54 +0100
> From: Hans Aberg <address@hidden>
> Are you saying that POSIX specifies how "/" should be interpreted in a
> C/C++ #include statement?

Sure it does.  For example, POSIX specifies that "#include
<sys/types.h>" should work.

But we are quibbling.  I don't think we should go through all GNU code,
or even some GNU code, worrying about this.  The hosts in question are
not of primary interest to the GNU project and are obsolescent to boot.

In this particular case, though, the fix seems easy, and I don't think
it'll hurt anything.

> Are you saying that one now always gets an error when YYSTACK_USE_ALLOCA is
> not defined?

No.  It works as before, pretty much (there are some fixes).

> Therefore, while waiting for the full C++ support, this seems to be a
> reasonable thing. -- It does not look that difficult to do.

Yes; please see my previous message.  I'd appreciate it if you'd test
its patch for C++.

> BTW, should not really bison.simple be named simple.bison, following the
> common usage for filename extensions? (That is, it is a file to the Bison
> skeleton language.)

Perhaps, but I wouldn't change the name now; it's not worth the hassle.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]