From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12686 invoked by alias); 11 Aug 2008 15:09:26 -0000 Received: (qmail 12673 invoked by uid 22791); 11 Aug 2008 15:09:26 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 11 Aug 2008 15:08:51 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m7BF8kwx017301; Mon, 11 Aug 2008 11:08:46 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m7BF8j3k012857; Mon, 11 Aug 2008 11:08:45 -0400 Received: from opsy.redhat.com (vpn-10-8.bos.redhat.com [10.16.10.8]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m7BF8jc4028897; Mon, 11 Aug 2008 11:08:45 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 08B65378159; Mon, 11 Aug 2008 09:08:48 -0600 (MDT) To: "Paul Pluzhnikov" Cc: gdb-patches@sourceware.org Subject: Re: [RFC] [patch] 'p->x' vs. 'p.x' and 'print object on' References: <20080717214839.6AE253A67B6@localhost> <8ac60eac0807301050id1051q8072925c0d11b96d@mail.gmail.com> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Mon, 11 Aug 2008 15:09:00 -0000 In-Reply-To: <8ac60eac0807301050id1051q8072925c0d11b96d@mail.gmail.com> (Paul Pluzhnikov's message of "Wed\, 30 Jul 2008 10\:50\:24 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2008-08/txt/msg00299.txt.bz2 >>>>> "Paul" == Paul Pluzhnikov writes: Paul> C) Do what the language does: lookup field 'x' in the static type, Paul> and only try dynamic type if the first lookup failed: It occurred to me last night that we must be careful not to do this in the overload resolution case. Looking at extra overloads from the dynamic type will yield the wrong answer. I think these code paths are separate in gdb, so that should not be a big deal, but I thought it would be good to be explicit about it. Tom