From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Jonny Grant <jg@jguk.org>, libc-alpha@sourceware.org
Subject: Re: glibc strerrorname_np
Date: Tue, 9 Nov 2021 22:37:26 -0300 [thread overview]
Message-ID: <2fb103f7-8c65-ea9f-65bb-92ce14839fe1@linaro.org> (raw)
In-Reply-To: <00c5d718-eaca-886c-ac02-73879c745a56@jguk.org>
On 09/11/2021 20:01, Jonny Grant wrote:
> Ok I see.
> It's also tricky as I'd prefer to not define _GNU_SOURCE
>
> What do you think of the possiblity of adding something like strerrorname() directly without _GNU_SOURCE, and always returning a valid string, or empty string?
>
> With a consistent return for an errnum of 0.
> strerror_r(0, &b, 0); already returns "".
> strerror(0) returns "Success"
>
> So there is some inconsistency in the POSIX functions.
The problem of exporting it without being a GNU extension (within _GNU_SOURCE
namespace) is that it might clash with a future POSIX interface. I need to
check where exactly POSIX defines it, but if I recall correctly it defines
specific namespace rules for the POSIX defined headers.
next prev parent reply other threads:[~2021-11-10 1:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 20:23 Jonny Grant
2021-11-04 20:46 ` Adhemerval Zanella
2021-11-04 22:52 ` Jonny Grant
2021-11-04 23:28 ` Adhemerval Zanella
2021-11-05 11:51 ` Jonny Grant
2021-11-05 13:01 ` Adhemerval Zanella
2021-11-05 22:23 ` Jonny Grant
2021-11-06 12:51 ` Adhemerval Zanella
2021-11-07 17:37 ` Zack Weinberg
2021-11-08 13:56 ` Adhemerval Zanella
2021-11-08 18:42 ` Zack Weinberg
2021-11-08 18:52 ` Adhemerval Zanella
2021-11-08 19:56 ` Florian Weimer
2021-11-08 20:28 ` Adhemerval Zanella
2021-11-08 22:22 ` Jonny Grant
2021-11-09 12:30 ` Adhemerval Zanella
2021-11-09 23:01 ` Jonny Grant
2021-11-10 1:37 ` Adhemerval Zanella [this message]
2021-11-08 8:36 ` Florian Weimer
2021-11-08 13:36 ` Jonny Grant
2021-11-08 13:42 ` Florian Weimer
2021-11-08 22:14 ` Jonny Grant
2021-11-08 14:01 ` Adhemerval Zanella
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=2fb103f7-8c65-ea9f-65bb-92ce14839fe1@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=jg@jguk.org \
--cc=libc-alpha@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).