> From: "Todd C. Miller" <todd.mil...@courtesan.com> > Date: Tue, 18 Feb 2014 14:50:53 -0700 > > On Tue, 18 Feb 2014 16:38:07 -0500, Ted Unangst wrote: > > > True, I phrased that poorly. What I'm assuming is that the code will > > be built by a compiler that supports the const keyword. Or in other > > words, if you're using a 25 year old cross compiler, I don't think > > it's unreasonable to expect you to dig up a 25 year old cross yacc > > either (or the yacc from openbsd 5.4). > > > > Who is actually using yacc to generate code for a compiler that > > doesn't accept const? > > Sudo 1.7.x still compiles on K&R, mostly for the benefit of the > bundled HP-UX compiler that has C89 support disabled.
There is only one reason that compiler exists: tuning kernel parameters (which requires recompiling a trivial C file and linking it into a new kernel). It should not be used for any other other purpose. It is horribly buggy. That said, I don't understand why tedu is wasting his time on this. If it isn't broken, don't fix it. Like Theo said, people shouldn't be looking at .c code produced by yacc.
