From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25007 invoked by alias); 29 Nov 2013 15:27:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 24994 invoked by uid 89); 29 Nov 2013 15:27:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 29 Nov 2013 15:27:50 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id rATFRgoC028392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 29 Nov 2013 10:27:43 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id rATFRfMx013245; Fri, 29 Nov 2013 10:27:42 -0500 Message-ID: <5298B26D.5070705@redhat.com> Date: Fri, 29 Nov 2013 17:22:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Phil Muldoon CC: gdb-patches@sourceware.org Subject: Re: [RFC] Python's gdb.FRAME_UNWIND_NULL_ID is no longer used. What to do with it? References: <1385664356-29726-1-git-send-email-palves@redhat.com> <5297B2BF.9010401@redhat.com> In-Reply-To: <5297B2BF.9010401@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-11/txt/msg00938.txt.bz2 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