<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/18/2018 03:37 PM, Eric S. Raymond
via devel wrote:<br>
cite="mid:20180618203746.GG26566@thyrsus.com">Ah, now that's the
kind of error pattern I *expect* from Bison parsers.
The underlying problem is that the C in Bison parser skeletons is
really archaic. It dates from times when not even the value of
procedural encapsulation was fully understood - thus all those ugly
globals hanging out in front of God and everybody.
It's not actually in the least difficult to design a skeleton that
gets this right. I did it once. The point is that that warning is nothing
we're doing wrong, it's GCC correctly noticing that the skeleton code kinda
sucks, and we probably *would* have to build a custom skeleton to
fix it. I have seen this movie before.
So why haven't the skeletons been fixed in all this time? The only
reasons I can see are Write Once Forget Forever, and unwillingness
to use more modern features that not all projects are able to use
(which could be an option switch).<br>
<div class="moz-signature">-- <br>
<i>"In the end; what separates a Man, from a Slave? Money? Power?
No. A Man Chooses, a Slave Obeys."</i> -- Andrew Ryan
<i>"Utopia cannot precede the Utopian.
It will exist the moment we are fit to occupy it."</i> --
I work for the <a href="https://icei.org/">Internet Civil
Engineering Institute</a>, help us save the Internet from