From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sourceware.org
Subject: Re: asynchronous MI output commands
Date: Tue, 09 May 2006 21:48:00 -0000 [thread overview]
Message-ID: <20060509143454.GB20120@brasko.net> (raw)
In-Reply-To: <20060508012615.GA22814@nevyn.them.org>
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
next prev parent reply other threads:[~2006-05-09 14:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 1:26 Bob Rossi
2006-05-06 1:59 ` Daniel Jacobowitz
2006-05-06 2:48 ` Bob Rossi
2006-05-06 3:37 ` Nick Roberts
2006-05-06 15:20 ` Bob Rossi
2006-05-06 4:06 ` Daniel Jacobowitz
2006-05-06 4:05 ` Daniel Jacobowitz
2006-05-06 11:53 ` Bob Rossi
2006-05-06 12:06 ` Bob Rossi
2006-05-06 3:14 ` Bob Rossi
2006-05-06 4:04 ` Nick Roberts
2006-05-06 11:49 ` Daniel Jacobowitz
2006-05-06 11:50 ` Bob Rossi
2006-05-06 16:52 ` Daniel Jacobowitz
2006-05-06 19:45 ` Bob Rossi
2006-05-06 20:37 ` Daniel Jacobowitz
2006-05-07 0:44 ` Bob Rossi
2006-05-07 20:35 ` Daniel Jacobowitz
2006-05-07 20:42 ` Bob Rossi
2006-05-07 22:01 ` Daniel Jacobowitz
2006-05-08 1:22 ` Bob Rossi
2006-05-08 2:03 ` Daniel Jacobowitz
2006-05-09 21:48 ` Bob Rossi [this message]
2006-05-08 6:38 ` Nick Roberts
2006-05-08 11:28 ` Bob Rossi
2006-05-08 1:26 ` Bob Rossi
2006-05-06 11:51 ` Bob Rossi
2006-05-06 3:27 ` Nick Roberts
2006-05-06 16:40 ` Bob Rossi
[not found] <1147034156.28828.ezmlm@sourceware.org>
2006-05-07 21:27 ` Bjarke Viksoe
2006-05-07 21:41 ` Daniel Jacobowitz
2006-05-10 12:43 ` Vladimir Prus
2006-05-07 22:30 Bjarke Viksoe
2006-05-07 22:50 ` Daniel Jacobowitz
2006-05-08 0:36 ` Bjarke Viksoe
2006-05-08 1:52 ` Daniel Jacobowitz
2006-05-09 9:46 Alain Magloire
2006-05-10 22:15 Alain Magloire
2006-05-11 3:41 ` Bob Rossi
2006-05-11 8:58 ` Vladimir Prus
2006-05-11 10:48 ` Bob Rossi
2006-05-11 10:52 ` Vladimir Prus
2006-05-11 11:14 ` Bob Rossi
2006-05-11 12:50 ` Vladimir Prus
2006-05-11 14:50 ` Bob Rossi
2006-05-11 15:02 Alain Magloire
2006-05-11 15:42 ` Bob Rossi
2006-05-11 16:40 ` Jim Ingham
2006-05-11 17:03 ` Daniel Jacobowitz
2006-05-11 17:35 ` Jim Ingham
2006-05-11 19:24 ` Bob Rossi
2006-05-11 19:25 ` Jim Ingham
2006-05-12 0:19 Alain Magloire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060509143454.GB20120@brasko.net \
--to=bob_rossi@cox.net \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox