From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Zack Weinberg <zackw@panix.com>
Cc: mtk.manpages@gmail.com, Mike Frysinger <vapier@gentoo.org>,
linux-mtd@lists.infradead.org,
GNU C Library <libc-alpha@sourceware.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] makedev(3): point people at sys/sysmacros.h
Date: Wed, 20 Apr 2016 12:39:00 -0000 [thread overview]
Message-ID: <57177853.8020006@gmail.com> (raw)
In-Reply-To: <CAKCAbMiMNtMmCP4EPZnZ5DpSNaNc=SDbbdKKZmoRybmWHyOoTg@mail.gmail.com>
On 04/20/2016 01:47 PM, Zack Weinberg wrote:
> On Wed, Apr 20, 2016 at 7:31 AM, Michael Kerrisk (man-pages)
> <mtk.manpages@gmail.com> wrote:
>> On 04/19/2016 06:52 AM, Mike Frysinger wrote:
>>> Defining these functions via sys/types.h violates POSIX namespace
>>> requirements,
>>
>> What do the previous lines mean? Violate namespace requirements how?
>
> I think it's technically not true that they violate POSIX namespace
> requirements, since they're only defined in the non-conforming modes.
>
> The reason I originally proposed the change is that libstdc++
> force-enables _GNU_SOURCE, which means people writing in C++ _can't_
> avoid these nonstandard macros by using a strict conformance mode.
Thanks for the explanation, Zack. I applied Mike's patch.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2016-04-20 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460860245-14895-1-git-send-email-vapier@gentoo.org>
2016-04-18 16:39 ` [PATCH mtd-utils] include sys/sysmacros.h for major/minor/makedev Brian Norris
2016-04-18 16:49 ` Mike Frysinger
2016-04-19 5:52 ` [PATCH] makedev(3): point people at sys/sysmacros.h Mike Frysinger
2016-04-20 11:31 ` Michael Kerrisk (man-pages)
2016-04-20 11:48 ` Zack Weinberg
2016-04-20 12:39 ` Michael Kerrisk (man-pages) [this message]
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=57177853.8020006@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier@gentoo.org \
--cc=zackw@panix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).