From: Craig Howland <howland@LGSInnovations.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
<newlib@sourceware.org>
Subject: Re: [PATCH] Use __BSD_VISIBLE for RTEMS <sys/_termios.h>
Date: Wed, 24 May 2017 14:51:00 -0000 [thread overview]
Message-ID: <ce5e6a14-126d-b02a-9c72-e52bfae257be@LGSInnovations.com> (raw)
In-Reply-To: <f96a94a6-bc2e-032b-ed5c-701a7f78d5d1@embedded-brains.de>
On 05/24/2017 05:29 AM, Sebastian Huber wrote:
> On 24/05/17 07:42, Sebastian Huber wrote:
>
>> On 23/05/17 17:16, Craig Howland wrote:
>>> On 05/23/2017 04:23 AM, Sebastian Huber wrote:
>>>> The Termios header <sys/_termios.h> used _POSIX_SOURCE directly to
>>>> determine if a thing should be exposed to the user. This circumvented
>>>> the feature mechanisms of <sys/cdefs.h>.
>>> Would you please explain why !_POSIX_SOURCE being replaced with
>>> __BSD_VISIBLE rather than, for example, !__POSIX_VISIBLE?
>>
>> A negation of visibility define makes no sense.
>>
>>> That is, you seem to not only be updating to sys/features.h macro names, but
>>> also shifting exactly how the gate is done. (I'm not saying it is
>>> necessarily incorrect, just that the explanation does not mention the logic
>>> change. The two are not logical opposites, so an implication is that the
>>> original gate of POSIX is not really the right one.)
>>
>> This is an import from FreeBSD. To me this looks like FreeBSD forgot to
>> update the Termios headers to use the visibility defines.
>>
>> https://lists.freebsd.org/pipermail/freebsd-hackers/2017-May/051069.html
>>
>
> I changed this in FreeBSD:
>
> https://svnweb.freebsd.org/base?view=revision&revision=318780
>
> I will send a v2 of the patch set for Newlib.
>
Yaakov agreed with BSD as the gate, and I also independently found a source
which says VEOL2, VWERASE, etc. are BSD extensions; __BSD_VISIBLE is good.
prev parent reply other threads:[~2017-05-24 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 8:23 Sebastian Huber
2017-05-23 15:16 ` Craig Howland
2017-05-23 21:20 ` Yaakov Selkowitz
2017-05-24 5:42 ` Sebastian Huber
2017-05-24 9:29 ` Sebastian Huber
2017-05-24 14:51 ` Craig Howland [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=ce5e6a14-126d-b02a-9c72-e52bfae257be@LGSInnovations.com \
--to=howland@lgsinnovations.com \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).