>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
> I installed the following patch in the hope of addressing the issues > involved. I couldn't make it quite as clean as the glr.c version due > to backward compatibility issues with alloca. Frankly, is alloca really worth so much trouble here? If it needs to grow the stack then we waste space; actually a statically allocated stack might be preferable is the matter is to save some calls to the OS (no no no, I'm not proposing an additional memory management scheme!). I hardly believe there are environments, even embedded, that support alloca but not malloc. So what is exactly the point of striving for alloca? alloca is a great tool to simplify the deallocation, but that's not our case. alloca provides speed improvement, but is it really measurable in the case of a parser?
