From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21166 invoked by alias); 3 Apr 2009 15:16:25 -0000 Received: (qmail 21158 invoked by uid 22791); 3 Apr 2009 15:16:24 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout6.012.net.il (HELO mtaout6.012.net.il) (84.95.2.16) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Apr 2009 15:16:18 +0000 Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KHJ00M0067YLE00@i-mtaout6.012.net.il> for gdb-patches@sourceware.org; Fri, 03 Apr 2009 18:16:15 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.171.54]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KHJ007YZ6F2ZE30@i-mtaout6.012.net.il>; Fri, 03 Apr 2009 18:16:15 +0300 (IDT) Date: Fri, 03 Apr 2009 15:16:00 -0000 From: Eli Zaretskii Subject: Re: Python pretty-printing [3/6] In-reply-to: To: Tom Tromey Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: X-IsSubscribed: yes 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 X-SW-Source: 2009-04/txt/msg00066.txt.bz2 > From: Tom Tromey > Date: Thu, 02 Apr 2009 14:55:41 -0600 > > 2009-04-01 Thiago Jung Bauermann > Tom Tromey > > * gdb.texinfo (Types From Inferior): New node. > (Python API): Update. Thanks. Comments: > +@node Types From Inferior > +@subsubsection Types From Inferior Some @cindex entry here would be good. > The base types of C++ classes are also Please use "C@t{++}", it looks better in print. > +@item bitpos > +This attribute is not available for @code{static} fields. For > +non-@code{static} fields, the value is the bit position of the field. What are "static fields"? Should that be explained here? > +@item type > +The type of the field. This is usually an instance of @code{Type}, > +but it can be @code{None} in some situations. Should we tell what are those situations where you get "None", or at least give an example or two? > +@defmethod Type tag > +Return the tag name for this type. The tag name is the name after > +@code{struct}, @code{union}, or @code{enum} in C; not all languages > +have this concept. Should we talk about more than just C? (I assume that at least one more language has some of these tag names.) > +For a pointer type, the target type is the type of the pointed-to > +object. For an array type, the target type is the type of the > +elements of the array. For a function type, the target type is the > +type of the return value. For a complex type, the target type is the > +type of the elements. For a typedef, the target type is the aliased > +type. Again, this sounds specific to C and C++; isn't there something useful we can tell for other languages, like Ada or Pascal or Java? > +@defmethod Type template_argument n > +If this @code{gdb.Type} is a template type, this will return a new > +@code{gdb.Type} which represents the type of the @var{n}th template > +argument. Is this C++-specific? If so, what will happen in other languages? > +@item TYPE_CODE_METHOD > +A C++ method type. Would it make sense to call it TYPE_CODE_CPP_METHOD, to make more clear that it's C++-specific (is it?)? Likewise for other C++-specific constants described below.