From: Zack Weinberg <zackw@panix.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
Date: Mon, 22 May 2017 22:54:00 -0000 [thread overview]
Message-ID: <CAKCAbMidoO2AmiSH0rjLPuRHApHQK=0HmFJjgAkLu584rHPOzQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705221132250.21862@digraph.polyomino.org.uk>
On Mon, May 22, 2017 at 7:32 AM, Joseph Myers <joseph@codesourcery.com> wrote:
> Ping. This patch
> <https://sourceware.org/ml/libc-alpha/2017-05/msg00484.html> is pending
> review.
So I'm OK with __ versions of NGREG, NFPREG, etc, but is it really
necessary to mangle structure field names? Is it just to defend
against user definitions of those identifiers as preprocessor macros,
or is there a more likely-to-happen-in-real-code reason, given the
general tendency to avoid object-like macros nowadays?
zw
next prev parent reply other threads:[~2017-05-22 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:42 Joseph Myers
2017-05-22 11:32 ` Ping " Joseph Myers
2017-05-22 22:54 ` Zack Weinberg [this message]
2017-05-23 6:30 ` Florian Weimer
2017-05-23 11:53 ` Joseph Myers
2017-06-01 11:37 ` Ping^2 " Joseph Myers
2017-06-01 12:20 ` Adhemerval Zanella
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='CAKCAbMidoO2AmiSH0rjLPuRHApHQK=0HmFJjgAkLu584rHPOzQ@mail.gmail.com' \
--to=zackw@panix.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).