From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-90213-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 6035 invoked by alias); 23 Apr 2012 15:05:41 -0000
Received: (qmail 6016 invoked by uid 22791); 23 Apr 2012 15:05:39 -0000
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Apr 2012 15:05:25 +0000
Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0M2X00M00TSJYC00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Mon, 23 Apr 2012 18:05:17 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.229.249.186]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M2X00MPVTWSUS40@a-mtaout21.012.net.il>; Mon, 23 Apr 2012 18:05:17 +0300 (IDT)
Date: Mon, 23 Apr 2012 16:00:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC - Python scripting] New methods Symtab.global_block and Symtab.static_block (docs included)
In-reply-to: <4F95630D.1000202@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: tromey@redhat.com, sivachandra@google.com, dje@google.com, ratmice@gmail.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83vckqfpzb.fsf@gnu.org>
References: <CAGyQ6gyuJ1oYBH3O5gzNc7Y7NK7AGC2F9a8Z3ts4dMm0GpVy0g@mail.gmail.com> <831unms3jy.fsf@gnu.org> <CAGyQ6gxxEeYeCKw_iHXh74Gg223GHxMoW=gvt9kU+ax396kKBQ@mail.gmail.com> <CAGyQ6gy+i4Tdh4zWDi_+cR+kw3MiU23BvWXgBqu5-+E48rjssw@mail.gmail.com> <4F8F187D.3050402@redhat.com> <878vhsojgd.fsf@fleche.redhat.com> <CAGyQ6gzC_2hZfhBv4SQNGVem0bOLxMp+02Nmy=iwPtqNE=J8kg@mail.gmail.com> <CADPb22TvvQDSA1EL4ydoZRGkKBm1kTCGcHyB2dc3X28p8XqyAg@mail.gmail.com> <CAGyQ6gzK7FvC0EYvJD+DGnCRssbNREoSjdROfpbv0u22sBNOKQ@mail.gmail.com> <CACTLOFrp7Hg0ZG8h=NVkyjD-_400Zv=Zdrf2Lq_OW-ga=qiTbw@mail.gmail.com> <87sjfyi5rj.fsf@fleche.redhat.com> <CADPb22RMzJpQDGhDU3b=R_sL2y_wd5y+qGJ+1t0sqbNWioPn9w@mail.gmail.com> <CAGyQ6gxAs2i+f0K5SGKV2h+Ltg439PVYSRuuD1BcMCGObi20Wg@mail.gmail.com> <87lilmh9jf.fsf@fleche.redhat.com> <4F95595A.8080106@redhat.com> <83y5pmft8k.fsf@gnu.org> <4F95630D.1000202@redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2012-04/txt/msg00748.txt.bz2

> Date: Mon, 23 Apr 2012 15:11:25 +0100
> From: Phil Muldoon <pmuldoon@redhat.com>
> CC: tromey@redhat.com, sivachandra@google.com, dje@google.com,
>         ratmice@gmail.com, gdb-patches@sourceware.org
> 
> I am just not sure we should have compatibility warnings that the
> content/structure of these blocks may change in some undefined way,
> at some future time.

With that I agree.  Saying such things in a manual is never a good
idea, unless we also describe in detail what exactly can go wrong, how
to detect that, and how to work around.