From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9009 invoked by alias); 9 May 2006 14:34:26 -0000 Received: (qmail 8998 invoked by uid 22791); 9 May 2006 14:34:26 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao02.cox.net (HELO eastrmmtao02.cox.net) (68.230.240.37) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 09 May 2006 14:34:21 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060509143417.OUHA15470.eastrmmtao02.cox.net@localhost.localdomain> for ; Tue, 9 May 2006 10:34:17 -0400 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1FdTIc-0004xJ-H9 for gdb@sourceware.org; Tue, 09 May 2006 10:34:54 -0400 Date: Tue, 09 May 2006 21:48:00 -0000 From: Bob Rossi To: gdb@sourceware.org Subject: Re: asynchronous MI output commands Message-ID: <20060509143454.GB20120@brasko.net> References: <20060506114933.GF25114@brasko.net> <20060506152046.GA24267@nevyn.them.org> <20060506164030.GK25114@brasko.net> <20060506165249.GA25972@nevyn.them.org> <20060506194618.GL25114@brasko.net> <20060506203741.GA29439@nevyn.them.org> <20060507004518.GM25114@brasko.net> <20060507212711.GA18344@nevyn.them.org> <20060508002935.GN25114@brasko.net> <20060508012615.GA22814@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060508012615.GA22814@nevyn.them.org> User-Agent: Mutt/1.5.9i X-IsSubscribed: yes 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-05/txt/msg00096.txt.bz2 On Sun, May 07, 2006 at 09:26:15PM -0400, Daniel Jacobowitz wrote: > On Sun, May 07, 2006 at 08:29:35PM -0400, Bob Rossi wrote: > > OK. I start with the MI output. I use bison to convert that into an > > abstract parse tree. Now, I am working on a solution to take the > > abstract parse tree and turn it into a simple to use representation for > > the front end (ADT). I gave the example earlier, taking the abstract parse > > tree for -file-list-exec-source-file > > ^done,line="26",file="test.c",fullname="/home/bob/cvs/cgdb/cgdb.mi/builddir/test.c" > > and turn that into > > struct file_list_exec_source_file > > { > > int line; > > char *file; > > char *fullname; > > }; > > struct file_list_exec_source_file result = { 26, "test.c", "/home..."}; > > [What's ADT mean then? The "A" can't be abstract, there's nothing > abstract about this.] Oops, my terminology is off again. I'm sorry. I'll try to do better in the future. I simply want to create a specific struct for each MI output command. I'm making some progress on this task. I'm going to post what I've got in a few days. I'm not happy with the way it's turning out, due to the fact that the MI output commands don't describe what kind of output command they are. However, with comments from you and Nick, I'm sure I can work it out. Thanks, Bob Rossi