From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22881 invoked by alias); 24 Aug 2004 20:18:05 -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 22840 invoked from network); 24 Aug 2004 20:18:04 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 24 Aug 2004 20:18:04 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i7OKHrS2024458 for ; Tue, 24 Aug 2004 16:18:03 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7OKHra21528; Tue, 24 Aug 2004 16:17:53 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C18B12B9D; Tue, 24 Aug 2004 16:16:44 -0400 (EDT) Message-ID: <412BA22C.1000106@gnu.org> Date: Tue, 24 Aug 2004 20:18:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Bob Rossi Cc: Michael Chastain , gdb-patches@sources.redhat.com Subject: Re: GDB/MI Output syntax References: <20040824191931.GC17542@white> <412B980A.nailFLQ1QDS6L@mindspring.com> <412B9B2C.3080302@gnu.org> <20040824200116.GF17865@white> In-Reply-To: <20040824200116.GF17865@white> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00670.txt.bz2 > On Tue, Aug 24, 2004 at 03:46:52PM -0400, Andrew Cagney wrote: > >>>> >Bob Rossi wrote: >>>> > >>> >>>>>> >>>-@code{@var{async-record} | @var{stream-record}} >>>>>> >>>+@code{( @var{async-record} | @var{stream-record} ) @var{nl}} >>> >>>> > >>>> > >>>> >I'm dubious about this. >>>> > >>>> >stream-record does not have an NL terminator and needs one, yes. >>>> > >>>> >But async-record already gets an NL terminator in the grammar >>>> >and does not need a second one. >> >>> >>> That's kind of why, per my earlier post, I suggested moving all the >>> @var{nl} to the @var{output} production. That way we can see exactly >>> where they fit in. > > > Andrew, were you suggesting something like this? > > from > output ==> ( out-of-band-record )* [ result-record ] "(gdb)" nl > to > output ==> (out-of-band-record nl)* [ result-record nl] "(gdb)" nl > > and removing the 'nl' everywhere else? Yep. > That might actually work. Although, I don't personally know a way of > changing a grammar and guaranteeing that there the same. A series of rewrites where NL is slow pushed down should eventually result in the old grammar (well except that it would be fixed). Andrew