From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sivachandra@google.com, gdb-patches@sourceware.org
Subject: Re: [RFC - doc] Add note about the possibility of symbols getting moved across blocks
Date: Thu, 26 Apr 2012 14:04:00 -0000 [thread overview]
Message-ID: <87397qa9a0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83y5pjedjp.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Apr 2012 23:56:10 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> I meant what should I do or not do as the user of the Python API in
Eli> question.
Eli> Or maybe I misunderstand what you are saying, sorry.
I think the idea is to warn Python developers that they should test
their code with future versions if they use this feature.
Normally we try to maintain compatibility, even when we've made mistakes.
But in this case, we suspect we may make changes and we don't want to
promise compatibility; but nor do we want to block this feature until
the symbol tables are changed, since that may not happen for some time.
I'm not totally wedded to this. Maybe Doug could say more.
Tom
next prev parent reply other threads:[~2012-04-26 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 8:13 Siva Chandra
2012-04-25 9:02 ` Eli Zaretskii
2012-04-25 20:02 ` Tom Tromey
2012-04-25 21:02 ` Eli Zaretskii
2012-04-26 14:04 ` Tom Tromey [this message]
2012-04-26 14:17 ` Eli Zaretskii
2012-04-27 13:15 ` Siva Chandra
2012-04-27 15:38 ` Eli Zaretskii
2012-04-27 16:59 ` Doug Evans
2012-04-27 17:33 ` Eli Zaretskii
2012-04-27 17:46 ` Doug Evans
2012-04-27 19:42 ` Siva Chandra
2012-04-28 7:15 ` Eli Zaretskii
2012-04-30 19:20 ` Siva Chandra
2012-05-02 17:32 ` 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=87397qa9a0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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