From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] New files "memory.[hc]"
Date: Mon, 27 Oct 2003 16:24:00 -0000 [thread overview]
Message-ID: <1031027162402.ZM29516@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [rfc] New files "memory.[hc]"" (Oct 27, 10:39am)
On Oct 27, 10:39am, Andrew Cagney wrote:
> > On Oct 24, 4:48pm, Andrew Cagney wrote:
> >
> >> What do people think of putting the new (with target parameter) methods,
> >> that wrap target_{read,write} in a new file "memory.[hc]"? I think they
> >> are going to end up cluttering up "target.[hc]".
> >
> > Sounds okay to me.
>
> But is it a good idea, as in will it make the code easier to read, find,
> and understand? The old target-memory routines are all "hidden" (well i
> think they are :-) in gdbcore.h and corefile.c
I know it's kind of long, but how about "target-memory.[hc]" ?
Kevin
next prev parent reply other threads:[~2003-10-27 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 20:48 Andrew Cagney
2003-10-24 21:04 ` Kevin Buettner
2003-10-27 15:39 ` Andrew Cagney
2003-10-27 16:24 ` Kevin Buettner [this message]
2003-10-30 20:28 ` 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=1031027162402.ZM29516@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.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