From: Keith Seitz <keiths@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] GDB interpreters
Date: Fri, 24 May 2002 16:20:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0205241531580.29198-100000@makita.cygnus.com> (raw)
In-Reply-To: <3CEEB81A.2010407@cygnus.com>
On Fri, 24 May 2002, Andrew Cagney wrote:
> Do you have a [working] draft? It is hard to see how it hangs together
> with out some additional context. Consider doing what I did and drop
> the work in progress onto a branch.
Yeah, I've got a massive set of changes that a compilation of this from
Apple and some of my own changes. (Most of my own changes are just
cosmetic: move things to separate files and whatnot. Apple crammed
everything in mi-main.c)
> The things I'm wondering about are:
>
> - how the ``struct gdb_interpreter'' gets called (can it be opaque?).
> There is a comment talking about how it is tied into the event loop.
These are completely opaque. Although Apple has a public definition of it
in interpreter.h, I was going to move it into interpreter.c. The only way
the code accessing this structure is via accessor functions
(gdb_interpreter_display_prompt, gdb_interpreter_set_quiet, etc).
> - what goes with hooks (I get the feeling that it is caught in the
> middle between ..._hook and gdb-event*)
Apple is using only hooks. It was my intent to swap it all to events, so
that all of the events/hooks are located in one place.
> Perhaphs consider a name other than interpreter.[hc]. Something to
> reflect that this isn't ``the'' interpreter but rather a part of the
> interpreters. terps? :-^ interps?
Ok, I think that's valid: interps.h and interps.c (unless I hear
otherwise).
> > static struct gdb_interpreter *interp_list = NULL;
> > static struct gdb_interpreter *current = NULL;
>
> Suggest ``current_interpreter''.
Very good.
> > static int initialized = 0;
>
> Same.
Ok.
>
> > /* gdb_new_interpreter - This allocates space for a new interpreter,
> > * fills the fields from the inputs, and returns a pointer to the
> > * interpreter. */
>
> I think it is ment to be:
>
> /* .....
> ..... */
>
> i.e. no `*' on each line.
Yes. Hmm. Does gdb_indent.sh catch this? I though I ran it on the files
before submitting them. Oh well, no matter. I'll double check for this.
Thanks for the comments.
Keith
next prev parent reply other threads:[~2002-05-24 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 13:46 Keith Seitz
2002-05-20 22:10 ` Eli Zaretskii
2002-05-21 9:14 ` Keith Seitz
2002-05-21 9:23 ` Keith Seitz
2002-05-21 13:27 ` Keith Seitz
2002-05-21 18:41 ` Eli Zaretskii
2002-05-24 15:00 ` Andrew Cagney
2002-05-24 15:38 ` Andrew Cagney
2002-05-24 16:20 ` Keith Seitz [this message]
2002-05-28 17:26 ` Keith Seitz
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=Pine.GSO.4.33.0205241531580.29198-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/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