public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>
Cc: libc-alpha@sourceware.org, "Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
Date: Tue, 23 May 2017 06:30:00 -0000	[thread overview]
Message-ID: <3b9dc796-5bdf-f3ce-92a0-a3558b00e152@redhat.com> (raw)
In-Reply-To: <CAKCAbMidoO2AmiSH0rjLPuRHApHQK=0HmFJjgAkLu584rHPOzQ@mail.gmail.com>

On 05/23/2017 12:54 AM, Zack Weinberg wrote:
> 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,

I think this is sufficient reason to do it, unfortunately.

> or is there a more likely-to-happen-in-real-code reason, given the
> general tendency to avoid object-like macros nowadays?

I don't think that tendency exists.  Maybe for some projects, but not
for glibc's upstreams (standards).

Thanks,
Florian

  reply	other threads:[~2017-05-23  6:30 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
2017-05-23  6:30     ` Florian Weimer [this message]
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=3b9dc796-5bdf-f3ce-92a0-a3558b00e152@redhat.com \
    --to=fweimer@redhat.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).