From: Doug Evans <dje@google.com>
To: Michael Snyder <msnyder@vmware.com>,
Jon Beniston <jon@beniston.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Patch to support spaces in filenames & paths
Date: Wed, 03 Dec 2008 00:26:00 -0000 [thread overview]
Message-ID: <e394668d0812021625n241552ffp77db75642deb602@mail.gmail.com> (raw)
In-Reply-To: <20081202233738.GA15530@caradoc.them.org>
On Tue, Dec 2, 2008 at 3:37 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Dec 02, 2008 at 01:17:22PM -0800, Michael Snyder wrote:
>> Denis, is it possible that Jon's patch will serve in place of
>> the filename portion of your patch? And that you could then
>> resubmit your patch with just the other portions?
>>
>> Jon's patch:
>> http://sourceware.org/ml/gdb-patches/2008-12/msg00032.html
>>
>> Denis' patch:
>> http://sourceware.org/ml/gdb-patches/2008-12/msg00029.html
>
> I have not looked at the patches in depth but I encourage Denis's
> approach - uniform parsing is a Very Good Thing and buildargv is what
> we use elsewhere.
While perhaps not applicable in Denis' case (since the command accepts
"a b c" instead of "a, b, c" (though I wonder if it could accept
both), for completeness' sake there is also parse_to_comma_and_eval.
(gdb) printf "%d %d %d\n", 1 + 1, 2 + 2, 3 + 3
2 4 6
With buildargv it'd be
(gdb) printf "%d %d %d\n" "1 + 1" "2 + 2" "3 + 3"
and that just doesn't sit right. :-)
next prev parent reply other threads:[~2008-12-03 0:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 13:09 Jon Beniston
2008-12-02 21:20 ` Michael Snyder
2008-12-02 23:38 ` Daniel Jacobowitz
2008-12-03 0:04 ` Pedro Alves
2008-12-03 0:26 ` Doug Evans [this message]
2008-12-04 9:38 ` Denis PILAT
2008-12-04 13:11 ` Daniel Jacobowitz
2008-12-10 15:32 ` Denis PILAT
2008-12-10 16:20 ` Daniel Jacobowitz
2009-01-05 14:20 ` Denis PILAT
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=e394668d0812021625n241552ffp77db75642deb602@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jon@beniston.com \
--cc=msnyder@vmware.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