[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison 1.30f
From: |
Hans Aberg |
Subject: |
Re: Bison 1.30f |
Date: |
Thu, 13 Dec 2001 10:43:30 +0100 |
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.
The principal designer BS thinks it's a low level hack that should not be
used; discussions in the comp.std.c++ newsgroup indicated it will not
become a part of the future C++ standard.
I do not know if alloca is a part of C99, though.
BTW, when using malloc, what stack re-allocation policy is the Bison
generated parser using? -- The thing is if one doubles the stack for every
new memory allocation, then time allocation complexity becomes linear.
Hans Aberg
- Re: Bison 1.30f, (continued)
- Re: Bison 1.30f, Axel Kittenberger, 2001/12/11
- Re: Bison 1.30f, Akim Demaille, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/12
- Re: Bison 1.30f, Akim Demaille, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/12
- Re: Bison 1.30f, Paul Eggert, 2001/12/12
- Re: Bison 1.30f,
Hans Aberg <=
- Re: Bison 1.30f, Akim Demaille, 2001/12/13
- Re: Bison 1.30f, Hans Aberg, 2001/12/13
- Re: Bison 1.30f, Akim Demaille, 2001/12/13
- Message not available
- Bison & C++, Hans Aberg, 2001/12/13
- Re: Bison & C++, Axel Kittenberger, 2001/12/13
- Re: Bison & C++, Hans Aberg, 2001/12/13
- Re: Bison 1.30f, Mike Castle, 2001/12/12
- Re: Bison 1.30f, Akim Demaille, 2001/12/13
- Re: Bison 1.30f, Paul Eggert, 2001/12/10
- Re: Bison 1.30f, Hans Aberg, 2001/12/11