[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C99 in Bison
From: |
Joel E. Denny |
Subject: |
Re: C99 in Bison |
Date: |
Wed, 2 Sep 2009 23:05:11 -0400 (EDT) |
User-agent: |
Alpine 1.00 (DEB 882 2007-12-20) |
On Wed, 2 Sep 2009, Akim Demaille wrote:
> Le 31 août 09 à 17:42, Joel E. Denny a écrit :
>
> > Hi Akim.
> >
> > On Mon, 31 Aug 2009, Akim Demaille wrote:
> >
> > > > Alternatively, we could poll at help-bison and might get an answer
> > > > faster.
> > >
> > > Yes, but what's the size of the poll?
> >
> > I just checked the subscriber list and it's 260.
>
> Wow, much larger than I expected. I should pay more attention to what I'm
> writing :)
Scary, isn't it? :-) I wonder how many watch bison-patches.
> So there are several polls:
>
> - c90 for generated yacc parsers (btw, the open group specs for yacc say
> "write C source code, conforming to the ISO C standard", which is unclear bw
> c90 and c99, but excludes any requirement to support knr).
Ah, I didn't think to check open group. It also has this line:
The C source code and header file shall be produced in a form suitable
as input for the C compiler (see c99).
> - remove the availability to reach the parse-params from the %printer and
> %destructor, at least in lalr1.cc.
>
> - ?
Maybe also a request for feedback on Bison's many experimental features.
> > By the way, I'm not able to look at the subscriber lists for bug-bison and
> > bison-patches. Why is that?
>
> No idea. The manager of the list may decide who can see the subscribers
> (anybody|subscribers|manager) but I don't know what rule the fsf follows.
Oh well. I doubt I'll pursue that further.