From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [RFC][python] Add support for commands implemented in Python
Date: Fri, 06 Feb 2009 22:12:00 -0000 [thread overview]
Message-ID: <1233952717.14735.113.camel@localhost.localdomain> (raw)
In-Reply-To: <uprhwt7fd.fsf@gnu.org>
El vie, 06-02-2009 a las 08:18 +0200, Eli Zaretskii escribió:
> > From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> > Cc: gdb-patches@sourceware.org
> > Date: Thu, 05 Feb 2009 20:40:05 -0200
> >
> > gdb/doc/
> > 2009-02-05 Tom Tromey <tromey@redhat.com>
> >
> > * gdb.texinfo (Python API): Add entry for Commands In Python.
> > (Commands In Python): New node.
>
> Thanks. My only comment to the new text is that perhaps the COMMAND_*
> constants should have followed the respective GDB command classes more
> closely. For example, COMMAND_RUNNING instead of COMMAND_RUN,
> COMMAND_DATA instead of COMMAND_VARS, etc. But that's a minor
> concern, especially if you had a good reason to deviate from the GDB
> interactive nomenclature.
I like your idea, I'm not sure if there was good reason for the
deviation other than that it was already present in the GDB source code
already. Tom, what do you think?
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-02-06 22: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 [this message]
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
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=1233952717.14735.113.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--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