From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4175 invoked by alias); 3 Sep 2009 19:19:10 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 4165 invoked by uid 22791); 3 Sep 2009 19:19:09 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org From: Tom Tromey To: Jan Kratochvil Cc: Project Archer , Chris Moller , Keith Seitz Subject: Re: [Keith Seitz] Re: [tools-team] Status 2008-09-01 References: <20090902214348.GA32564@host0.dyn.jankratochvil.net> Reply-To: Tom Tromey Date: Thu, 03 Sep 2009 19:19:00 -0000 In-Reply-To: <20090902214348.GA32564@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed, 2 Sep 2009 23:43:48 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2009-q3/txt/msg00173.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> Just this is due the wrong printing defaults: Jan> (gdb) p obj->num_ Jan> There is no member or method named num_. Jan> (gdb) set print object on Jan> (gdb) p obj->num_ Jan> $1 = 2 I'm really surprised that "set print object" affects this. It seems to me that this should always follow the language rules, and that "obj->num_" should therefore be an error. (I used to hold the opposite position for Java, funnily enough, but I have come around.) Instead I would expect this to work: (gdb) set print object on (gdb) print *obj $1 = ... # something of type special_int_math (gdb) print $.num_ $2 = whatever That is, I think "set print object on" ought to affect the type of the resulting history variable -- but not the type of any intermediate values in an expression. Jan> One should change this (+some other related options in Jan> `user_print_options') and in some way fix the testsuite regressions Jan> afterwards by one of: I agree, we should change this default. Tom