From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21219 invoked by alias); 23 Jan 2008 14:41:15 -0000 Received: (qmail 21210 invoked by uid 22791); 23 Jan 2008 14:41:14 -0000 X-Spam-Check-By: sourceware.org Received: from imr1.ericy.com (HELO imr1.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Jan 2008 14:39:07 +0000 Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m0NEd3Dm015358; Wed, 23 Jan 2008 08:39:03 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 08:39:03 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Patch] Fix for -var-update to use natural format to compare Date: Wed, 23 Jan 2008 14:41:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04290E55@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <18326.35603.281821.709393@kahikatea.snap.net.nz> From: "Marc Khouzam" To: "Nick Roberts" Cc: "Daniel Jacobowitz" , 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/msg00547.txt.bz2 >> In DSF, we (sometimes) display all values at once. Can be nice for the = user. >=20 > You say it "Can be nice for the user." but you haven't really answered the > first question: >=20 > why do you want to keep track of the value in all formats? >=20 > Why, for example, would a user want to see the value of a double as a > decimal? It just seems to be a misleading thing to do. Users will be users :-) But you make a good point. The answer can be found in http://dev.eclipse.org/mhonarc/lists/dsdp-dd-dev/msg01004.html which I copied here: "The DSF GDB debugger uses the detail pane in the variables, registers, and= =20 expressions views to display the variable in all available formats at the s= ame time. There is a bigger issue here though. The architecture of the debugger=20 integration in Eclipse separates the UI code (views, actions, etc) and the= =20 non-UI code with an API that abstracts the details of the debugger back end. However, GDB's design of the variable objects makes some assumptions about = the presentation of the data in the UI, and these assumptions are making it=20 somewhat difficult to create an efficient implementation of the non-UI lay= er=20 of the debugger integration. " So, to paraphrase, in DSF don't make any assumptions on what the UI will=20 request, but instead, we give the UI the possibility to request any of the= =20 formats at any time, without restrictions. Hope this clarifies a bit. Marc