From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <vladimir@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Make -exec-run and -exec-until into 'real' MI commands
Date: Thu, 14 Jan 2010 04:46:00 -0000 [thread overview]
Message-ID: <20100114044603.GS2007@adacore.com> (raw)
In-Reply-To: <20100113202620.GB3955@caradoc.them.org>
> I suggest asking for a second opinion then. I don't think this
> quoting is good enough to be a good idea. I think we can get away
> without it for -exec-run. I don't know about -exec-until.
I agree that we should avoid a quoting mechanism if it leads to
surprising results. There is some code that does quoting in fork-child,
perhaps we could reuse that code?
--
Joel
next prev parent reply other threads:[~2010-01-14 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:29 Vladimir Prus
2010-01-13 13:44 ` Marc Khouzam
2010-01-13 15:00 ` Vladimir Prus
2010-01-13 20:10 ` Daniel Jacobowitz
2010-01-13 20:13 ` Vladimir Prus
2010-01-13 20:26 ` Daniel Jacobowitz
2010-01-14 4:46 ` Joel Brobecker [this message]
2010-02-22 14:24 ` Vladimir Prus
2010-02-25 17:25 ` Joel Brobecker
2010-02-22 14:23 ` Vladimir Prus
2010-02-24 7:34 ` Vladimir Prus
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=20100114044603.GS2007@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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