Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Python's gdb.FRAME_UNWIND_NULL_ID is no longer used.  What to do with it?
Date: Fri, 29 Nov 2013 17:22:00 -0000	[thread overview]
Message-ID: <5298B26D.5070705@redhat.com> (raw)
In-Reply-To: <5297B2BF.9010401@redhat.com>

On 11/28/2013 09:16 PM, Phil Muldoon wrote:

> As a script could check it, and because we make an API promise, we
> really have to leave it in there.  You have done the correct
> thing by documenting the deprecated nature of the constant.
> 
> It might be time to think about what the API pertains too.  GDB
> evolves constantly, and I really don't want Python in a few years from
> now to be full of deprecated functions/constants.
> 
> OK by me.

Thanks guys.  I've pushed it.

-- 
Pedro Alves


  reply	other threads:[~2013-11-29 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 20:13 Pedro Alves
2013-11-28 21:16 ` Eli Zaretskii
2013-11-28 23:01 ` Phil Muldoon
2013-11-29 17:22   ` Pedro Alves [this message]
2013-12-02 16:10 ` Tom Tromey
2013-12-12 17:25   ` Pedro Alves
2013-12-12 17:37     ` Pedro Alves

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=5298B26D.5070705@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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