From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20629 invoked by alias); 17 Feb 2006 19:59:15 -0000 Received: (qmail 20332 invoked by uid 22791); 17 Feb 2006 19:59:14 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao06.cox.net (HELO eastrmmtao06.cox.net) (68.230.240.33) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Feb 2006 19:59:09 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao06.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060217195907.WLUE9108.eastrmmtao06.cox.net@localhost.localdomain>; Fri, 17 Feb 2006 14:59:07 -0500 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1FABkz-00057x-6T; Fri, 17 Feb 2006 14:59:09 -0500 Date: Fri, 17 Feb 2006 20:05:00 -0000 From: Bob Rossi To: Eli Zaretskii Cc: Vladimir Prus , gdb@sources.redhat.com Subject: Re: MI: type prefixes for values Message-ID: <20060217195909.GA19387@brasko.net> Mail-Followup-To: Eli Zaretskii , Vladimir Prus , gdb@sources.redhat.com References: <200602171658.23427.ghost@cs.msu.su> <200602171724.03824.ghost@cs.msu.su> <20060217190418.GA27304@nevyn.them.org> <20060217193556.GA28754@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i 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/msg00203.txt.bz2 On Fri, Feb 17, 2006 at 09:52:46PM +0200, Eli Zaretskii wrote: > > Date: Fri, 17 Feb 2006 14:35:56 -0500 > > From: Daniel Jacobowitz > > Cc: Vladimir Prus , gdb@sources.redhat.com > > > > Writing a grammar for it would be difficult-to-impractical. > > It doesn't need to be a formal grammar, just a spec that is accurate > enough to build a reader. > > MI should have a regular syntax which allows such a spec. If MI > doesn't support that, then it misses its main design goal. I completly disagree. MI has a design spec that allows a FE to parse the output of GDB. The data that it get's back from GDB is a whole different story. I expect that data to be useable at best by the front end. Bob Rossi