From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32100 invoked by alias); 17 Feb 2006 13:54:58 -0000 Received: (qmail 32092 invoked by uid 22791); 17 Feb 2006 13:54:57 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 17 Feb 2006 13:54:54 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FA64R-0004qL-UK for gdb@sourceware.org; Fri, 17 Feb 2006 08:54:52 -0500 Date: Fri, 17 Feb 2006 13:54:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: MI: type prefixes for values Message-ID: <20060217135451.GA18533@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <200602171329.34297.ghost@cs.msu.su> <200602171450.16858.ghost@cs.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00171.txt.bz2 On Fri, Feb 17, 2006 at 03:49:33PM +0200, Eli Zaretskii wrote: > I don't see how is this contrary to what GDB assumes. GDB passes the > information to the front end; how the front end displays it, is > entirely up to the front end. The interesting thing to learn from this conversation, IMO, is that a frontend is likely to show the type separately from the value. So maybe we should provide value= and type= if we want to provide both. The GDB CLI chooses to show types for some kinds of variables, and not for others. That's its perogative, but exposing that CLI decision over MI seems like a bad idea. There's plenty of other things like this. For instance, IIRC, the MI value output will include the annotations used by the CLI in some cases. -- Daniel Jacobowitz CodeSourcery