From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24301 invoked by alias); 4 Jan 2007 21:48:16 -0000 Received: (qmail 24289 invoked by uid 22791); 4 Jan 2007 21:48:15 -0000 X-Spam-Check-By: sourceware.org Received: from heller.inter.net.il (HELO heller.inter.net.il) (192.114.186.73) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 04 Jan 2007 21:48:09 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-66-129.inter.net.il [80.230.66.129]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id BLJ69639 (AUTH halo1); Thu, 4 Jan 2007 23:48:03 +0200 (IST) Date: Thu, 04 Jan 2007 21:48:00 -0000 Message-Id: From: Eli Zaretskii To: Vladimir Prus CC: drow@false.org, gdb-patches@sources.redhat.com In-reply-to: (message from Vladimir Prus on Thu, 04 Jan 2007 21:23:00 +0300) Subject: Re: [doc] improve MI varobj introduction Reply-to: Eli Zaretskii References: <200612191103.55137.vladimir@codesourcery.com> <200612210914.45128.vladimir@codesourcery.com> <20061226153206.GA16188@nevyn.them.org> <200612261851.55429.vladimir@codesourcery.com> <20061226223756.GA26777@nevyn.them.org> 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: 2007-01/txt/msg00151.txt.bz2 > From: Vladimir Prus > Date: Thu, 04 Jan 2007 21:23:00 +0300 > > Here's the final patch. Thanks. I have a few comments and suggestions. > -When returning the actual values of the objects, this facility allows > -for the individual selection of the display format used in the result > -creation. It can be chosen among: binary, decimal, hexadecimal, octal > -and natural. Natural refers to a default format automatically > -chosen based on the variable type (like decimal for an @code{int}, hex > -for pointers, etc.). This fragment was removed, but the new text doesn't mention this feature at all. Was the old text plain wrong (i.e. there's no such feature)? If the feature does exist, I think it should be mentioned. > +Variable object is MI interface to work with expressions. Perhaps it's an interface to work with named expressions, because I believe you don't need anything to work with just expressions, do you? > +object operations -- for example to obtain or change the value of Please use 3 dashes in a row, and without blanks on either side, to get an em-dash in the printed version. > +Variable objects have hierarchical structure. The original text said it was a tree structure. I suggest to add the ``tree'' part back (i.e. ``hierarchical tree structure''), as otherwise it is not clear why you talk about leaf variables further down. > Child variable objects can children themself, > +util we reach leaf variable objects of built-in types. ^^^^^^^^ ^^^^ Typos, and also something's wrong with this sentence in general. > +obtained for a non-leaf variable object, but its generally a string ^^^ "it's" > +that only indicates the type of the object, and does not list its > +content. ^^^^^^^ "contents". > +A frontend need not read the values of all variable objects each time ^^^^^^^^ "does not need" > +the program stops. Instead, MI provides update command that lists all ^^^^^^^^^^^^^^ "an update command" > +variable objects which values has changed since the last update ^^^^^^^^^^^^ "whose values" > +list of variable objects which values have changed. Here, ^^^^^^^^^^^^ Ditto.