This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)

From: Zack Weinberg <zackw at panix dot com>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Mon, 22 May 2017 18:54:04 -0400
Subject: Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
Authentication-results: sourceware.org; auth=none
References: <alpine.DEB.2.20.1705161742240.14609@digraph.polyomino.org.uk> <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

Follow-Ups:
- Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
  - From: Florian Weimer
- Re: Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
  - From: Joseph Myers

References:
- Fix more namespace issues in sys/ucontext.h (bug 21457)
  - From: Joseph Myers
- Ping Re: Fix more namespace issues in sys/ucontext.h (bug 21457)
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]