From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb@sources.redhat.com, drow@false.org
Subject: Re: GDB/MI Output Syntax ambiguity
Date: Mon, 23 Aug 2004 21:42:00 -0000 [thread overview]
Message-ID: <412A64E9.nailD781GRTXW@mindspring.com> (raw)
In-Reply-To: <20040823210924.GA22417@nevyn.them.org>
It's been a while since I wrote a yacc grammar, but my inclination
would be to enhance the lexer and distinguish some new terminals:
TOKEN-UPARROW
TOKEN-STAR
TOKEN-PLUS
TOKEN-EQUALS
Then the grammar goes from LALR(2) to LALR(1), because
result-record can start with TOKEN-UPARROW, which is just
one symbol, rather than token "^", which is two symbols.
That ought to make it yacc-parseable.
That keeps the token numbers in the natural place.
With drow's rule:
output -> [token] ( out-of-band-record-1 [token] )* [ result-record ] "(gdb)" nl
This is also LALR(1), but the token symbol is not bundled with
the wrong out-of-band-record-1, so the tree-value-constructing
code gets a little skewed.
But I'm rusty on all this.
next prev parent reply other threads:[~2004-08-23 21:42 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 [this message]
2004-08-23 22:23 ` Bob Rossi
2004-08-24 3:56 ` Michael Chastain
2004-08-24 12:36 ` Bob Rossi
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=412A64E9.nailD781GRTXW@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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