From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: Importing inttypes methods
Date: Mon, 31 Jul 2017 10:08:00 -0000 [thread overview]
Message-ID: <20170731100835.GL24013@calimero.vinschen.de> (raw)
In-Reply-To: <CAC82fA0ydpr6DMHjn=rYNqJHGB+YnNk9myH2oDihrtj61ZfkxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Jul 30 11:41, Gedare Bloom wrote:
> All,
>
> It looks like to me like the str*_l functions in stdlib.h currently
> are actually being guarded by __GNU_VISIBLE rather than __BSD_VISIBLE.
> You should see if these locale functions from BSD are in glibc, if so
> then I believe GNU_VISIBLE is the more appropriate guard? Someone more
> knowledgeable on the feature test macros might comment.
Yes, the functions are guarded with __GNU_VISIBLE, just as in glibc.
No, the {str,wcs}to{i,u}max_l functions are not defined in glibc at all,
so they should be __BSD_VISIBLE.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-07-31 10:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 19:51 Aditya Upadhyay
2017-07-26 11:08 ` Corinna Vinschen
2017-07-26 12:02 ` Sebastian Huber
2017-07-26 12:02 ` Aditya Upadhyay
2017-07-26 21:24 ` Aditya Upadhyay
2017-07-27 12:32 ` Corinna Vinschen
2017-07-27 14:00 ` Aditya Upadhyay
2017-07-28 10:43 ` Corinna Vinschen
2017-07-28 11:02 ` Aditya Upadhyay
2017-07-28 11:40 ` Gedare Bloom
2017-07-28 13:08 ` Corinna Vinschen
2017-07-28 14:28 ` Gedare Bloom
2017-07-28 18:29 ` Corinna Vinschen
2017-07-29 12:40 ` Gedare Bloom
2017-07-29 13:57 ` Aditya Upadhyay
2017-07-30 8:46 ` Aditya Upadhyay
2017-07-30 15:41 ` Gedare Bloom
2017-07-31 10:08 ` Corinna Vinschen [this message]
2017-08-01 8:31 ` Aditya Upadhyay
2017-08-01 12:10 ` Gedare Bloom
2017-07-28 18:24 ` Joel Sherrill
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=20170731100835.GL24013@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).