From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: "struct target_ops" -> "struct gdbtarg" || "struct target"
Date: Thu, 09 Oct 2003 13:51:00 -0000 [thread overview]
Message-ID: <3F8567D2.3020902@redhat.com> (raw)
In-Reply-To: <3F856516.9020904@redhat.com>
> Hello,
>
> The current "target_ops" structure appeared with GDB 4. The original implementation containing only methods. Since then the target_ops have evolved to include data vis:
>
> struct section_table
> *to_sections;
> struct section_table
> *to_sections_end;
>
> I think, the vector should be re-named to "struct target" or "struct gdbtarg" (consistent with gdbarch, and more name space proof) so that it correctly reflects its current implementation.
>
> I'd like to do this now, before the target methods start being explicitly parameterized with their target vector.
I should note that an alternative is to have "struct gdbarch" as the
object and "struct target_ops" as the methods vis:
struct target
{
.. data elements ...;
const struct target_ops *ops;
};
Andrew
next prev parent reply other threads:[~2003-10-09 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 13:39 Andrew Cagney
2003-10-09 13:51 ` Andrew Cagney [this message]
2003-10-09 19:42 ` Jim Blandy
2003-10-09 20:52 ` Andrew Cagney
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=3F8567D2.3020902@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@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