From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26547 invoked by alias); 16 Feb 2004 23:27:16 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26530 invoked from network); 16 Feb 2004 23:27:15 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 16 Feb 2004 23:27:15 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5BC442B92; Mon, 16 Feb 2004 18:27:14 -0500 (EST) Message-ID: <403151D2.1060908@gnu.org> Date: Mon, 16 Feb 2004 23:27:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: Bob Rossi Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa:doco] Zap mi1 reference References: <402D2DF2.8030001@gnu.org> <20040213203704.GA654@white> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00449.txt.bz2 > On Fri, Feb 13, 2004 at 03:05:06PM -0500, Andrew Cagney wrote: > >> Hello, >> >> This removes a reference to "mi1" in the documentation. It's no longer >> tested (hence 'supported'). > > > I don't really know how I feel about dropping support for old mi > versions. Is that the plan for future versions of mi? Well, neither can GDB support broken parts of the interface indefinitly :-( The vague intent is to slowly phase in fixes while at the same time phasing out the testing and eventually the code for the old interfaces. This should give a separate ui writer a year or so of grace with any specific MI version. This goes with the assumption that separate UI authors are qualifying their interface against a specific GDB/MI version. > I think the MI functions should be backwards compatible. Are they? Theory or reality? In theory the output is largely upward compatible - code can discard unrecognized fields. In reality warts eventually start to appear. For instance, both: - using frame ID's with varobj - N:M breakpoints will impact significantly on the MI interface. Andrew