From: Mark Kettenis <kettenis@wins.uva.nl>
To: gdb@sources.redhat.com
Subject: [RFC] ptid_get_pid function vs. PIDGET macro
Date: Sat, 06 Oct 2001 05:58:00 -0000 [thread overview]
Message-ID: <200110061257.f96CvtZ00321@delius.kettenis.local> (raw)
Ever since Kevin introduced `struct ptid' we have, in addition to the
PIDGET, TIDGET and MERGEPID macros, a new set of functions ptid_build,
pid_to_ptid, ptid_get_pid, etc. AFAIK, we've never talked about a
policy how we're going to deal with them. IMHO we should try to
eliminate the redundancy, and deprecate the macros. Do we agree on
that?
Mark
next reply other threads:[~2001-10-06 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 5:58 Mark Kettenis [this message]
2001-10-08 15:54 ` Kevin Buettner
2001-10-09 22:28 ` Andrew Cagney
2001-10-10 0:01 ` Kevin Buettner
2001-10-10 14:02 ` Mark Kettenis
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=200110061257.f96CvtZ00321@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--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