From: Daniel Jacobowitz <drow@false.org>
To: Jim Ingham <jingham@apple.com>
Cc: Bob Rossi <bob_rossi@cox.net>, gdb@sources.redhat.com
Subject: Re: MI query questions
Date: Tue, 30 May 2006 21:15:00 -0000 [thread overview]
Message-ID: <20060530204553.GA23684@nevyn.them.org> (raw)
In-Reply-To: <6CF6F2BF-276F-4634-BA75-80698EEE64EE@apple.com>
On Tue, May 30, 2006 at 01:14:12PM -0700, Jim Ingham wrote:
> I also like this =read-one-line thingie, because it makes it explicit
> what's going on, namely something other than the MI is trying to read
> one line of input. So the FE should solicit a line of input from
> whoever it's getting that from in the command that caused this
> message to be delivered, and send it on...
While I agree at first look, on the other hand:
(A) It messes up pipelining. You can't throw five commands at GDB at
once, if one of them might eat further input.
(B) It makes parsing the output somewhat trickier.
Would it be helpful to have some general solution for this, presumably
involving completions (i.e. closures)? Come back and answer the prompt
when you're ready?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-30 20:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 3:48 Bob Rossi
2006-05-30 8:20 ` Daniel Jacobowitz
2006-05-30 17:15 ` Jim Ingham
2006-05-30 17:41 ` Bob Rossi
2006-05-30 17:53 ` Jim Ingham
2006-05-30 17:55 ` Jim Ingham
2006-05-30 17:55 ` Bob Rossi
2006-05-30 18:12 ` Daniel Jacobowitz
2006-05-30 20:14 ` Jim Ingham
2006-05-30 18:27 ` Bob Rossi
2006-05-30 18:56 ` Jim Ingham
2006-05-30 20:46 ` Bob Rossi
2006-05-30 21:11 ` Jim Ingham
2006-05-30 21:15 ` Daniel Jacobowitz [this message]
2006-05-30 21:30 ` Jim Ingham
2006-05-31 9:38 ` Daniel Jacobowitz
2006-05-31 13:27 ` Bob Rossi
2006-05-30 17:00 ` Nick Roberts
2006-05-30 17:32 ` Bob Rossi
2006-05-31 10:29 ` Nick Roberts
2006-05-31 13:25 ` Bob Rossi
2006-06-01 0:58 ` Nick Roberts
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=20060530204553.GA23684@nevyn.them.org \
--to=drow@false.org \
--cc=bob_rossi@cox.net \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.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