Re: too many warnings from Bison CVS for Pike

[Paul Eggert]

Hans Aberg <address@hidden> writes:

> You are definitely wrong about that: Paul wrote the dynamic
> extensions, I recall.

No, Akim's right: the Yacc skeleton has supported dynamic reallocation
of the stack since 1993.  RMS is well-known for disliking arbitrary
limits, and one of the changes he installed in 1993, as compared to
the earlier skeleton by Corbett with a fixed-size stack, was support
for dynamic reallocation.  Like the current yacc.c, RMS's
implementation method used the equivalent of memcpy, so it was not
compatible with fancy C++ types.

This can all be easily verified by consulting the Bison CVS history.

> These are the parts you need to clear up,

It would be helpful to have better documentation.  I suggested on
February 14 in this thread that it would help if you would propose
specific patches, in "diff -u" format, and you wrote back that you'd
think about it.  Let's do that, instead of wasting further time
arguing about ancient history.

Please bear in mind that we want documentation that is short, simple,
and sweet.  Long explanations that talk about C++ versus C, the
ancient history of Bison, proper object-oriented style, name space
philosophy, etc., etc., are not likely to be accepted.  Personally, I
suspect this matter could be explained well in five lines or less.
(I'm not a C++ expert so I'm not the right person to write it.)