[Top][All Lists]

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

Re: Bison 1.30f

From: Akim Demaille
Subject: Re: Bison 1.30f
Date: 13 Dec 2001 11:39:58 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service)

>>>>> "Hans" == Hans Aberg <address@hidden> writes:

Hans> At 18:11 -0800 2001/12/12, Paul Eggert wrote:
>> alloca is notoriously nonstandardized, which is why "include
>> <alloca.h>" is so carefully protected in bison.simple.

Hans> The principal designer BS thinks it's a low level hack that
Hans> should not be used; discussions in the comp.std.c++ newsgroup
Hans> indicated it will not become a part of the future C++ standard.

We know, thanks.  But it's cool.

Hans> I do not know if alloca is a part of C99, though.

It is not, just as Paul wrote.

Hans> BTW, when using malloc, what stack re-allocation policy is the
Hans> Bison generated parser using? -- The thing is if one doubles the
Hans> stack for every new memory allocation, then time allocation
Hans> complexity becomes linear.

Hans, read TFC.

reply via email to

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