From: Sam James <sam@cmpct.info>
To: Sam James <sam@gentoo.org>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
Helge Kreutzmann <debian@helgefjell.de>,
GNU C Library <libc-alpha@sourceware.org>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page wcsncpy.3
Date: Sun, 4 Dec 2022 23:09:07 +0000 [thread overview]
Message-ID: <B67BFC03-D966-497B-94FC-499531EBE141@cmpct.info> (raw)
In-Reply-To: <EC7619DA-5D2E-4738-97D2-9A98D4108A02@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
> On 4 Dec 2022, at 23:06, Sam James via Libc-alpha <libc-alpha@sourceware.org> wrote:
>
>
>
>> On 4 Dec 2022, at 20:42, Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org> wrote:
>>
>> Hi Helge, glibc developers,
>>
>> On 12/4/22 10:07, Helge Kreutzmann wrote:
>>> Without further ado, the following was found:
>>> Issue: Is the "L" in the bracket (for the NULL character) correct?
>>> "The B<wcsncpy>() function is the wide-character equivalent of the"
>>> "B<strncpy>(3) function. It copies at most I<n> wide characters from the"
>>> "wide-character string pointed to by I<src>, including the terminating null"
>>> "wide character (L\\(aq\\e0\\(aq), to the array pointed to by I<dest>."
>>> "Exactly I<n> wide characters are written at I<dest>. If the length"
>>> "I<wcslen(src)> is smaller than I<n>, the remaining wide characters in the"
>>> "array pointed to by I<dest> are filled with null wide characters. If the"
>>> "length I<wcslen(src)> is greater than or equal to I<n>, the string pointed"
>>> "to by I<dest> will not be terminated by a null wide character."
>>
>> As an unrelated note. I've had this running in my mind for some time... your various bug reports for strncpy(3) and similar wide character functions have triggered those thougts.
>>
>> I'm going to mark strncpy(3) and similar functions as deprecated, even if no libc or standard has done so. There's wide agreement (at least in some communities) that strncpy(3) _is evil_. There's simply no use for it.
>>
>
> Please don't do this unilaterally. Apple did this unilaterally for sprintf which has caused problems, as well.
snprintf, that is
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2022-12-04 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221204090724.GA1249@Debian-50-lenny-64-minimal>
2022-12-04 20:42 ` Alejandro Colomar
2022-12-04 22:44 ` Alejandro Colomar
2022-12-04 23:06 ` Sam James
2022-12-04 23:09 ` Sam James [this message]
2022-12-04 23:28 ` Alejandro Colomar
2022-12-04 23:14 ` Alejandro Colomar
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=B67BFC03-D966-497B-94FC-499531EBE141@cmpct.info \
--to=sam@cmpct.info \
--cc=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
--cc=sam@gentoo.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).