Re: [RFC, PATCH] YACC parsers

[Mark Kettenis <mark.kettenis@xs4all.nl>]

> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 19 Dec 2011 08:07:49 -0700
> 
> >>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> 
> Mark> It may not be impossible to "fix" the OpenBSD yacc(4) here, but given
> Mark> the fact that it supports the -p option to add a prefix to all the
> Mark> relevant symbols that would be somewhat silly.  Unfortunately,
> Mark> changing the build infrastructure to use yacc -p isn't exactly
> Mark> trivial.
> 
> Mark> Opinions?
> 
> What is hard about using yacc -p?

As far as I can tell, it will require an explicit rule for each
parser, whereas currently an implicit rule is sufficient.

> I wouldn't mind getting rid of these hacks and requiring a -p-capable
> yacc.

POSIX requires the -p option, so I guess that would be fine.

> Or even requiring Bison; I think this would only be needed by gdb
> developers anyhow.

My primary development systems come with a perfectly fine yacc that
isn't bison.