From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org, gdb@sourceware.org
Subject: Re: Some Python ideas, looking for feedback
Date: Wed, 24 Aug 2011 09:48:00 -0000 [thread overview]
Message-ID: <4E54C8C6.3020309@ado.is-a-geek.net> (raw)
In-Reply-To: <m3vcttlca6.fsf@fleche.redhat.com>
On 19/08/11 15:13, Tom Tromey wrote:
>>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>
> Daniel> I don't suppose we can avoid exposing this internal C wart to Python,
> Daniel> and expose it some other way... ?
>
> I think it depends on whether we have shipped it or not.
> If we have, then perhaps someone is using it; in that case I would
> rather not break it.
Yes, you've shipped it. At least one person is using it (me). I'd
prefer it if this didn't go away.
> However, even in that case, we can still add a new attribute with a
> better name and recommend that people use it.
Thats fair enough, but for now can we please get the documentation updated?
--
Andrew Oakley
next prev parent reply other threads:[~2011-08-24 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 11:04 Paul_Koning
2011-08-16 11:45 ` André Pönitz
2011-08-16 14:45 ` Paul_Koning
2011-08-17 18:37 ` Andrew Oakley
2011-08-17 19:13 ` Andrew Oakley
2011-08-17 19:29 ` Eli Zaretskii
2011-08-17 19:35 ` Andrew Oakley
2011-08-17 20:38 ` Eli Zaretskii
2011-08-17 20:52 ` Daniel Jacobowitz
2011-08-17 21:15 ` Paul_Koning
2011-08-19 14:14 ` Tom Tromey
[not found] ` <CAN9gPaFPhVYmfUO0sZeMUUy0X7x+hyUd8wDFJZXbe98RVvTLSw__33957.6404345737$1313614343$gmane$org@mail.gmail.com>
2011-08-19 14:14 ` Tom Tromey
2011-08-24 9:48 ` Andrew Oakley [this message]
2011-08-24 11:42 ` Phil Muldoon
2011-08-24 11:46 ` Andrew Oakley
2011-08-24 16:17 ` Phil Muldoon
[not found] ` <m3aaazavdq.fsf__47025.4836873666$1314186175$gmane$org@redhat.com>
2011-08-25 17:59 ` Tom Tromey
2011-08-24 11:39 ` Phil Muldoon
2011-08-30 20:09 ` Tom Tromey
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=4E54C8C6.3020309@ado.is-a-geek.net \
--to=andrew@ado.is-a-geek.net \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@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