From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC][python] Add support for commands implemented in Python
Date: Wed, 04 Feb 2009 20:12:00 -0000 [thread overview]
Message-ID: <20090204201236.GA2263@caradoc.them.org> (raw)
In-Reply-To: <m3prhydl8e.fsf@fleche.redhat.com>
On Wed, Feb 04, 2009 at 01:02:09PM -0700, Tom Tromey wrote:
> An empty string would be fine by me. I initially chose None to
> parallel the C API, but it isn't clear how useful that is. An empty
> string is friendlier and doesn't seem to lose anything important.
Let's do that then.
> Does that answer your question? Or, if I'm misunderstanding
> something, could you say what? I looked at this again and I still
> don't see what might be wrong.
Thanks, that explains sub_list; an expanded comment would help. I was
confused about the use of parse_command_name - but now I see what it's
for.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-02-04 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 13:13 Thiago Jung Bauermann
2009-02-02 20:08 ` Eli Zaretskii
2009-02-04 19:50 ` Tom Tromey
2009-02-05 22:40 ` Thiago Jung Bauermann
2009-02-05 23:01 ` Tom Tromey
2009-02-06 6:18 ` Eli Zaretskii
2009-02-06 22:12 ` Thiago Jung Bauermann
2009-02-06 20:52 ` Tom Tromey
2009-02-06 21:35 ` Thiago Jung Bauermann
2009-02-07 10:02 ` Eli Zaretskii
2009-02-08 23:57 ` Thiago Jung Bauermann
2009-02-15 15:47 ` Thiago Jung Bauermann
2009-02-04 0:32 ` Daniel Jacobowitz
2009-02-04 20:02 ` Tom Tromey
2009-02-04 20:12 ` Daniel Jacobowitz [this message]
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=20090204201236.GA2263@caradoc.them.org \
--to=drow@false.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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