From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: strdup visibility
Date: Mon, 08 Feb 2021 01:21:25 -0500 [thread overview]
Message-ID: <29869ada38d29ae1d8eccdac5935a67daf7b035d.camel@cygwin.com> (raw)
In-Reply-To: <6d8bd601-10ef-5ae1-551d-0d9ea62ee49e@gmail.com>
On Mon, 2021-02-08 at 04:04 +0100, Marco Atzeri via Cygwin-developers wrote:
> currently we have in /usr/include/string.h
>
> #if __MISC_VISIBLE || __POSIX_VISIBLE >= 200809 || __XSI_VISIBLE >= 4
> char *strdup (const char *) __malloc_like __result_use_check;
> #endif
>
>
> but the function was moved to POSIX base some time ago
> https://pubs.opengroup.org/onlinepubs/9699919799/functions/strdup.html
>
> should the conditional dropped ? Or I misunderstand it?
Anything that is an extension in the ANSI C headers is conditionalized. Those
conditions match the progressive standardization of this function and it's
eventual inclusion in POSIX-1.2008.
Have you run into a real-world issue with these conditions?
--
Yaakov
next prev parent reply other threads:[~2021-02-08 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 3:04 Marco Atzeri
2021-02-08 6:21 ` Yaakov Selkowitz [this message]
2021-02-08 12:36 ` marco atzeri
2021-02-19 3:03 ` Yaakov Selkowitz
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=29869ada38d29ae1d8eccdac5935a67daf7b035d.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-developers@cygwin.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).