From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5451 invoked by alias); 22 Jan 2008 17:59:26 -0000 Received: (qmail 5439 invoked by uid 22791); 22 Jan 2008 17:59:26 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Jan 2008 17:59:03 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 7015A98375; Tue, 22 Jan 2008 17:59:01 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 4BB6B98216; Tue, 22 Jan 2008 17:59:01 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JHNOm-0003Bu-8u; Tue, 22 Jan 2008 12:59:00 -0500 Date: Tue, 22 Jan 2008 17:59:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [Patch] Fix for -var-update to use natural format to compare Message-ID: <20080122175900.GA12246@caradoc.them.org> Mail-Followup-To: Vladimir Prus , gdb-patches@sources.redhat.com References: <20080122150232.GA32509@caradoc.them.org> <6D19CA8D71C89C43A057926FE0D4ADAA04290E4A@ecamlmw720.eamcs.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) 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: 2008-01/txt/msg00527.txt.bz2 On Tue, Jan 22, 2008 at 08:49:53PM +0300, Vladimir Prus wrote: > It's good to improve docs in this way. It should be noted that this > might not be true in future, say when we add Python scripting, or > (maybe) when we'll add a way to specify floating point precision. Let's keep the documentation focused on what's true today - no point saying "this might not work someday" when there isn't an alternative yet. > > Also, if GDB requires this of frontends showing mutliple formats, it would > > be nice to have -var-evaluate-expression take a format as an optional > > parameter. Then, the frontend would not need to use -var-set-format > > to get a different formatted value, and could keep the variable object > > in the natural format at all times. > > > > I can provide a patch if this is a supported idea. > > I personally think this is a good idea! It means that if we for example > need to quickly show some value in specific format, like hex value in tooltip, > we don't need two format setting commands before and after. So, such > a patch will be valuable independently of how -var-update operates. I think this is a good idea too. -- Daniel Jacobowitz CodeSourcery