>> I don't see how K&R compat helps us. None of the headers in >> /usr/include are K&R anymore. How would one compile the generated output? > >You're assuming that the resulting code will be built on OpenBSD. >That's a bad assumption. The code generated by lex and yacc should >be as portable as possible.
Why??? The *.y file is the source code. the .c and .h files it generates are not the source code, but an intermediate language. To stetch this to the limit, we should be shipping cpp-processed files, for maximum portability. NO WAY! .y files should be the portable ones, and this entire decades old pattern of shipping y.tab.* files has been incredibly hurtful. After yacc became part of full operating systems, that practice served NO PURPOSE. I agree completely with removing the backwards compatibility.
