From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9073 invoked by alias); 30 Mar 2012 20:52:23 -0000 Received: (qmail 9065 invoked by uid 22791); 30 Mar 2012 20:52:22 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL,TW_XG X-Spam-Check-By: sourceware.org Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Mar 2012 20:52:08 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0M1P00300TOU9O00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Fri, 30 Mar 2012 23:52:06 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.100.223]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M1P003JUTYT6LB0@a-mtaout23.012.net.il>; Fri, 30 Mar 2012 23:52:06 +0300 (IDT) Date: Fri, 30 Mar 2012 20:52:00 -0000 From: Eli Zaretskii Subject: Re: set print object on should affect MI varobjs (PR mi/13393) In-reply-to: <4F761708.8080105@yandex.ru> To: xgsa Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83r4w9zua0.fsf@gnu.org> References: <4ED92C05.9080803@yandex.ru> <4EF22A4D.80703@yandex.ru> <20111221193630.GA28985@host2.jankratochvil.net> <4EF30389.5010008@yandex.ru> <20111223200951.GA19581@host2.jankratochvil.net> <4EF5D1C5.5010902@yandex.ru> <20120102022153.GA686@host2.jankratochvil.net> <4F07177C.5080201@yandex.ru> <4F32C009.2050103@yandex.ru> <87pqdma1mo.fsf@fleche.redhat.com> <4F412637.2010405@yandex.ru> <4F660CF6.9070008@yandex.ru> <8339953anu.fsf@gnu.org> <4F66DBD0.4000903@yandex.ru> <83vcm01obe.fsf@gnu.org> <4F6CADEF.4080700@yandex.ru> <83vclmynmz.fsf@gnu.org> <4F761708.8080105@yandex.ru> 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: 2012-03/txt/msg01073.txt.bz2 > Date: Fri, 30 Mar 2012 23:26:48 +0300 > From: xgsa > CC: gdb-patches@sourceware.org > > >> +would be printed by the @value{GDBN} CLI. Note that if > >> +@samp{set print object} setting is set the @emph{actual} (derived) type > >> +of the object is set rather than @emph{declared} one. > > "setting is set" is not right. I actually don't understand what you > > tried to say; if you explain your intent, I will suggest a better > > wording. > I meant that "set print object on/off" will also affect the "type" field > returned by -var-create and -var-list-children. > Probably, it should be an "option" not "setting". The result will look > like this: > > +would be printed by the @value{GDBN} CLI. Note that if > +@samp{set print object} option is set the @emph{actual} (derived) type > +of the object is set rather than @emph{declared} one. > > > Is it ok? Close, but not quite there yet. The last piece we need to clarify is the "actual (derived) type of the object is set" part. What do you mean by "type is set"? This text describes the result returned by '-var-create', so did you mean to say that the actual type is mentioned in the tuple returned by this operation? IOW, did you mean to point out that the 'type=TYPE' part of -var-create's output will mention the actual type as TYPE? Thanks.