From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24783 invoked by alias); 1 Mar 2012 17:36:39 -0000 Received: (qmail 24654 invoked by uid 22791); 1 Mar 2012 17:36:38 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,TW_VT,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Mar 2012 17:36:24 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q21HaN2k007098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 1 Mar 2012 12:36:24 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q21HaMjZ001559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 1 Mar 2012 12:36:23 -0500 From: Tom Tromey To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [4/5] implement "info vtable" References: <87mx82prmd.fsf@fleche.redhat.com> <4F4F8D39.60507@redhat.com> Date: Thu, 01 Mar 2012 17:36:00 -0000 In-Reply-To: <4F4F8D39.60507@redhat.com> (Pedro Alves's message of "Thu, 01 Mar 2012 14:52:41 +0000") Message-ID: <878vjkjka1.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.93 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-03/txt/msg00024.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> My only gripe is that we end up with the vtable vs vtbl inconsistency Pedro> (set print vtbl). Yeah. I was thinking of renaming 'set print vtbl' (keeping the old name as an alias of course). WDYT? I think "vtable" is both clearer and more commonly used. Pedro> May be a good idea if the docs are augmented a bit to give an example, Pedro> and lightly explain the output. Ok. Pedro> IIUC, "info vtable POINTER" works. The tests only sees to try Pedro> "info vtable OBJ". Worth adding a test that tries through a pointer? Will do. Tom