From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: Michael Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: GDB/MI Output syntax
Date: Tue, 24 Aug 2004 19:54:00 -0000 [thread overview]
Message-ID: <20040824195351.GE17865@white> (raw)
In-Reply-To: <412B9B2C.3080302@gnu.org>
On Tue, Aug 24, 2004 at 03:46:52PM -0400, Andrew Cagney wrote:
> >Bob Rossi <bob@brasko.net> wrote:
> >
> >>>-@code{@var{async-record} | @var{stream-record}}
> >>>+@code{( @var{async-record} | @var{stream-record} ) @var{nl}}
> >
> >
> >I'm dubious about this.
> >
> >stream-record does not have an NL terminator and needs one, yes.
> >
> >But async-record already gets an NL terminator in the grammar
> >and does not need a second one.
>
> That's kind of why, per my earlier post, I suggested moving all the
> @var{nl} to the @var{output} production. That way we can see exactly
> where they fit in.
I don't think it would be possible to move all of the @var{nl} to the
output production. Not without making the output production very large.
This is because in several case's the newline is only outputted
conditionally, since some productions are optional.
I think the simple patch would be fine for now. Do you agree?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2004-08-24 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 19:19 Bob Rossi
2004-08-24 19:33 ` Michael Chastain
2004-08-24 19:39 ` Bob Rossi
2004-08-24 19:43 ` Bob Rossi
2004-08-24 19:53 ` Michael Chastain
2004-08-24 19:48 ` Andrew Cagney
2004-08-24 19:54 ` Bob Rossi [this message]
2004-08-24 20:01 ` Bob Rossi
2004-08-24 20:18 ` Andrew Cagney
2004-08-24 20:56 ` Bob Rossi
2004-08-25 15:51 ` Andrew Cagney
2004-08-25 4:09 ` Eli Zaretskii
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=20040824195351.GE17865@white \
--to=bob@brasko.net \
--cc=cagney@gnu.org \
--cc=gdb-patches@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