From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8729 invoked by alias); 25 Jan 2008 14:16:13 -0000 Received: (qmail 8716 invoked by uid 22791); 25 Jan 2008 14:16:10 -0000 X-Spam-Check-By: sourceware.org Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Jan 2008 14:15:21 +0000 Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m0PEEw37029721; Fri, 25 Jan 2008 08:14:58 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Jan 2008 08:14:58 -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]: MI -var-set-format Date: Fri, 25 Jan 2008 15:46:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04290E65@ecamlmw720.eamcs.ericsson.se> In-Reply-To: From: "Marc Khouzam" To: "Eli Zaretskii" Cc: 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/msg00609.txt.bz2 =20 >> +To know if a variable object or any of its children has changed value i= n any=20 >> +format instead of only the current one, the variable object and all its= children >> +should be in the natural format before issuing the @code{-var-update} c= ommand.=20=20 > >Sorry, I don't understand what this sentence is trying to say. What >does it mean ``the object should be in the natural format before >issuing the command''? How can an object ``be'' in some format?=20=20 You are right about that. I should probably refer to 'display format' inst= ead. >And how would its format help me know that it changed its value? This is the tricky part. We had a loooong thread about this but writing it= in one or two sentences was not that easy. Maybe we should use an example? I'll explain it in plain text and when we reach an understandable text, I'l= l attach a new documentation patch. In some cases, the displayed value of a variable object may change in some,= but=20 not all of the possible display formats. For example, a variable object of= =20 type 'double', can change natural display from 1.1 to 1.9, while its hexade= cimal=20 display will remain at 0x1 in both cases. Therefore, if the variable objec= t has its current display format set to 'hexadecimal', the -var-update command wi= ll not list this object, as its current display has not changed.=20 If a frontend needs -var-update to list=20 variable objects for which the value has changed in any format (instead of = only=20 listing the ones for which the current displayed value has changed), the va= riable=20 object and all its children should have their current display format set to= natural=20 before issuing the -var-update command. [We believe that] if any formatted value changes, it guarantees that the na= tural format value will also change. Marc