From: Bob Rossi <bob@brasko.net>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB/MI Output Syntax ambiguity
Date: Tue, 24 Aug 2004 12:36:00 -0000 [thread overview]
Message-ID: <20040824123613.GC16751@white> (raw)
In-Reply-To: <412ABC62.nailDPO16U0B2@mindspring.com>
On Mon, Aug 23, 2004 at 11:56:18PM -0400, Michael Chastain wrote:
> [Shout out to Paul Hilfinger, who was my professor in compiler class,
> Spring 1983, UC Berkeley!]
>
> The grammar in gdb.info from gdb 6.2 has stuff like (foo)* and [bar] and is
> not quite low-level enough for bison input.
>
> I made a grammar out of it by expanding the (foo)* and [bar] stuff
> with rules. Appended is my grammar as I typed it in.
I will compare the grammar more in detail. However, these are the 5
rules I applied to get the MI grammar to not have any left recursions.
1. (out-of-band-record)* ->
out-of-band-record-prime -> out-of-band-record-list | epsilon
out-of-band-record-list -> out-of-band-record-list out-of-band-record | out-of-band-record
2. [result-record]
possible-result-record -> result-record | epsilon
3. [token]
possible-token -> token | epsilon
4. ( "," result )*
result-list-prime -> result-list | epsilon
result-list -> result-list "," result | "," result
5. ( "," value )*
value-list-prime -> value-list | epsilon
value-list -> value-list "," value | "," value
Other than that, I think it's all still the same.
I will compare the grammars in more detail today.
Thanks for putting in the great effort!
Bob Rossi
next prev parent reply other threads:[~2004-08-24 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 21:03 Bob Rossi
2004-08-23 21:09 ` Daniel Jacobowitz
2004-08-23 21:12 ` Bob Rossi
2004-08-23 21:37 ` Bob Rossi
2004-08-23 21:42 ` Michael Chastain
2004-08-23 22:23 ` Bob Rossi
2004-08-24 3:56 ` Michael Chastain
2004-08-24 12:36 ` Bob Rossi [this message]
2004-08-24 17:15 Xinan Tang
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=20040824123613.GC16751@white \
--to=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
/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