From: Mark Kettenis <kettenis@chello.nl>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: ARI `asection' and `sec_ptr'
Date: Sat, 01 Mar 2003 13:41:00 -0000 [thread overview]
Message-ID: <861y1r5hns.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Mon, 24 Feb 2003 11:20:02 -0500"
Daniel Jacobowitz <drow@mvista.com> writes:
> Thanks, that was what I was looking for. I still prefer asection,
> since it's the interface that binutils uses in exported interfaces, but
> I don't have a strong preference.
I really agree with Daniel here in that I think we should use the
types used in the interface definitions as much as possible. For
stuff internal to GDB we whould of course prefer `struct *foo' over
using a typedf `foo_ptr'.
Mark
next prev parent reply other threads:[~2003-03-01 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 6:41 Andrew Cagney
2003-02-24 14:25 ` Daniel Jacobowitz
2003-02-24 15:05 ` Andrew Cagney
2003-02-24 15:18 ` Daniel Jacobowitz
2003-02-24 15:40 ` Andrew Cagney
2003-02-24 15:49 ` Daniel Jacobowitz
2003-02-24 16:18 ` Andrew Cagney
2003-02-24 16:20 ` Daniel Jacobowitz
2003-03-01 13:41 ` Mark Kettenis [this message]
2003-03-01 15:13 ` 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=861y1r5hns.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=drow@mvista.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