Re: bison-20001221

[Hans Aberg]

At 20:12 +0100 1-01-22, Akim Demaille wrote:
>> Even though obstack memory management is claimed to be
>> efficient, it is not as efficient as it could be, because when
>> it runs out of stack,
>
>No, _my_ macros run out of stack with _your_ compiler :)

No, I was not referring to that problem, but the obstack.h summary:
  When the chars burst over a chunk boundary, we allocate a larger
  chunk, and then copy the partly formed object from the end of the old
  chunk to the beginning of the new larger chunk.  We then carry on
  accreting characters to the end of the object as we normally would.

But allowing characters to flow over a boundary is probably difficult to
achieve in C (easy in C++).

>> I think it would be interesting to implement
>> the open_obstack_stream function.
>
>I think you might be underestimating the difficulty of implementing
>printf-like functions.

OK. C isn't C++, where such things are easy. Let's skip this discussion, as
the main point is having eliminated the temp files.

  Hans Aberg