From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7292 invoked by alias); 6 Oct 2004 17:31:25 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7262 invoked from network); 6 Oct 2004 17:31:24 -0000 Received: from unknown (HELO NUTMEG.CAM.ARTIMI.COM) (217.40.111.177) by sourceware.org with SMTP; 6 Oct 2004 17:31:24 -0000 Received: from mace ([192.168.1.25]) by NUTMEG.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.0); Wed, 6 Oct 2004 18:31:03 +0100 From: "Dave Korn" To: "'Bob Rossi'" Cc: "'Eli Zaretskii'" , Subject: RE: probing GDB for MI versions Date: Wed, 06 Oct 2004 17:36:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20041006172138.GI12213@white> Message-ID: X-OriginalArrivalTime: 06 Oct 2004 17:31:03.0361 (UTC) FILETIME=[40E37B10:01C4ABCA] X-SW-Source: 2004-10/txt/msg00153.txt.bz2 > -----Original Message----- > From: 'Bob Rossi' > Sent: 06 October 2004 18:22 > I guess the bottom line is, I already have a parser that is capable of > dealing with a specific version of MI's output. I don't want > to start up > MI with an adhoc parser, just to figure out what real parser I should > use. This seems not correct to me, and I guess it's the issue to deal > with. It's absolutely correct. You have the tools for the job, but you need a piece of information in order to select the correct tool. Since you cannot use the tool to get the information to select the tool to .......... as you so correctly point out, the answer is to use a _different_ tool. And a crude ad-hoc parser is just the tool for the job. > The problem is, we would be adding a command to the MI > function set that > would not be able to be parsed and understood with an MI parser. This > seems really wrong to me. It's probably the issue we should be > discussing. There's no reason why your version-specific MI parsers shouldn't both be able to understand the output from the -mi-version command as well. But you will need the ad-hoc one to get started with. If you don't like the idea of an ad-hoc parser, you could always call it a "recognizer" instead...... cheers, DaveK -- Can't think of a witty .sigline today....