From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC, PATCH] YACC parsers
Date: Mon, 19 Dec 2011 16:13:00 -0000 [thread overview]
Message-ID: <m31us0woza.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201112191528.pBJFSCU5008408@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Mon, 19 Dec 2011 16:28:12 +0100 (CET)")
Mark> As far as I can tell, it will require an explicit rule for each
Mark> parser, whereas currently an implicit rule is sufficient.
Yeah, I see.
That isn't such a big deal. We can stuff the body of the rule into a
variable and reuse it in each explicit rule.
>> I wouldn't mind getting rid of these hacks and requiring a -p-capable
>> yacc.
Mark> POSIX requires the -p option, so I guess that would be fine.
Fine by me.
>> Or even requiring Bison; I think this would only be needed by gdb
>> developers anyhow.
Mark> My primary development systems come with a perfectly fine yacc that
Mark> isn't bison.
I suspect eventually I will have a reason to require bison, but we can
put that off until and if it ever happens.
Tom
prev parent reply other threads:[~2011-12-19 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 19:40 Mark Kettenis
2011-12-18 6:21 ` Joel Brobecker
2011-12-19 15:15 ` Tom Tromey
2011-12-19 15:39 ` Mark Kettenis
2011-12-19 16:13 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31us0woza.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox