[RFC, PATCH] YACC parsers

[Joel Brobecker]

> It may not be impossible to "fix" the OpenBSD yacc(4) here, but given
> the fact that it supports the -p option to add a prefix to all the
> relevant symbols that would be somewhat silly.  Unfortunately,
> changing the build infrastructure to use yacc -p isn't exactly
> trivial.
> 
> Opinions?

FWIW, We are already using those #defines for other symbols, so I don't
think that adding a few is going to make things worse.

-- 
Joel