From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29957 invoked by alias); 18 Mar 2006 02:40:23 -0000 Received: (qmail 29924 invoked by uid 22791); 18 Mar 2006 02:40:22 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 18 Mar 2006 02:40:20 +0000 Received: from kahikatea.snap.net.nz (p202-124-114-152.snap.net.nz [202.124.114.152]) by viper.snap.net.nz (Postfix) with ESMTP id 6F7ED74946D; Sat, 18 Mar 2006 15:40:10 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id EDAEF88EC; Sat, 18 Mar 2006 15:38:45 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17435.29362.640036.97752@kahikatea.snap.net.nz> Date: Tue, 21 Mar 2006 10:22:00 -0000 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: MI: type prefixes for values In-Reply-To: <20060318013113.GA28374@nevyn.them.org> References: <17427.54333.236860.258115@kahikatea.snap.net.nz> <20060317193243.GB19068@nevyn.them.org> <17435.24954.801098.804532@kahikatea.snap.net.nz> <20060318013113.GA28374@nevyn.them.org> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00237.txt.bz2 > > Unlike Volodya's change, its not a change in the MI protocol but one of > > presentation, so I would put it mi2 -i.e the curent default mi (recall that > > -i=mi sets mi_version to 2). I thought that Volodya was also adding a type field. > I don't think it makes a difference - it could confuse consumers of MI2 > anyway - that's all I'm worried about. I think it means its generally less likely to make a difference. In Emacs, I just take the value of the field amd insert it in the appropriate window at the appropriate place. Thats why the type currently gets duplicated in the locals window. Removing the type prefix just removes that duplication, I don't have to make any changes to the lisp code in Emacs. Adding a field, however, might break my parser if I'm not expecting it. However, perhaps you're thinking specifically of Eclipse. ... > > Since there are likely to be many more changes to MI, I suggest that when > > we start making changes for mi3 only, the default remains at mi2. This > > will allow a period of development for mi3 during which changes can be > > made more freely. It could then be made the default level after it has > > stabilised. > > Yes, this is already how we document -i=mi to work. It's the last > finalized version of the protocol. But there have been many changes to mi2, notably adding the fullname field in several places, since it became the default level. I'm just suggesting that we don't have mi4, mi5, mi6 etc because it gets too complicated. -- Nick http://www.inet.net.nz/~nickrob