From: Doug Evans <dje@google.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Siva Chandra <sivachandra@google.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC] A new command 'grep'
Date: Mon, 02 Jan 2012 17:44:00 -0000 [thread overview]
Message-ID: <CADPb22R5G=fkb9dVM3=2aRnOvtUpEuhqWXwNqWSZ3VQT-Dj3ig@mail.gmail.com> (raw)
In-Reply-To: <CAPftXUJ-gFL9dRYX9OWx9oaEhPSfMsBak_vu3Dk5P1-5xaWA4A@mail.gmail.com>
On Mon, Jan 2, 2012 at 1:28 AM, Kevin Pouget <kevin.pouget@gmail.com> wrote:
> On Mon, Jan 2, 2012 at 9:54 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> I think this is the first time we receive a proposal for a command
>> implemented in Python. Perhaps there's a place to discuss whether
>> some policy is in order in this regard. E.g., the command will be
>> unavailable in non-Python builds, which at least needs to be
>> documented. There may be other aspects that are worth discussing.
>
> I'm also curious about that, and maybe first of all, is there a Python
> specific coding convention likely to be enforced in GNU projects
> and/or GDB?
Sorry for the repeat.
[I wasn't aware the mail program I was using would sent it as rich html, sigh.]
For reference sake,
there are already some gdb commands in python,
see python/lib/gdb/command.
The pretty printer support there doesn't need to worry about
non-python builds of course.
As for coding convention, we follow pep008 with a few additions.
ref: http://sourceware.org/gdb/current/onlinedocs/gdbint/Coding-Standards.html#Coding-Standards
next prev parent reply other threads:[~2012-01-02 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 5:01 Siva Chandra
2012-01-02 8:54 ` Eli Zaretskii
2012-01-02 9:28 ` Kevin Pouget
2012-01-02 9:35 ` Abhijit Halder
2012-01-02 10:17 ` Siva Chandra
2012-01-02 17:44 ` Doug Evans [this message]
2012-01-03 6:02 ` Siva Chandra
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='CADPb22R5G=fkb9dVM3=2aRnOvtUpEuhqWXwNqWSZ3VQT-Dj3ig@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=sivachandra@google.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