From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25138 invoked by alias); 1 Jul 2009 21:05:15 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 25129 invoked by uid 22791); 1 Jul 2009 21:05:14 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4A4BCC63.5020407@googlemail.com> References: <20090701203842.32FE076BC0@localhost> <4A4BCC63.5020407@googlemail.com> Date: Wed, 01 Jul 2009 21:05:00 -0000 Message-ID: <8ac60eac0907011405r6013eb17q4afd0d98c740bb5a@mail.gmail.com> Subject: Re: How to distinguish inheritance from containment? From: Paul Pluzhnikov To: Richard Ward Cc: archer@sourceware.org, Tom Tromey Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-System-Of-Record: true X-SW-Source: 2009-q3/txt/msg00003.txt.bz2 On Wed, Jul 1, 2009 at 1:51 PM, Richard Ward wrote: > I sent a patch to archer that did just that about two weeks ago, if you want > it (not that it take that long to write one yourself). It had "Info about > base class in gdb.Type" in the subject line. Ah, missed it the first time. The patch looks good to me, except I think "inherited" is clearer than "base_class". If you don't like "inherited", perhaps "is_base_class" ? Also, you'll need a proper ChangeLog entry for both gdb/ChangeLog and gdb/doc/ChangeLog. Something like: ChangeLog: 2009-05-28 Richard Ward * python/python-type.c (convert_field): New attribute "base_class". doc/ChangeLog: 2009-05-28 Richard Ward * gdb.texinfo (Types In Python): Describe "base_class". Tom, any chance this could go in? Thanks, -- Paul Pluzhnikov