From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page wcsncpy.3
Date: Sun, 12 Mar 2023 00:23:20 +0100 [thread overview]
Message-ID: <c36c21ee-8244-a6fe-7bfb-2f4a2b61c5fc@gmail.com> (raw)
In-Reply-To: <20230311171357.GA4888@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
Hi Helge,
On 3/11/23 18:13, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: null wide characters → NUL wide characters?
This is incorrect. NUL is an ASCII character, which hasn't wide
characters. It's correct as "null wide characters", a.k.a. L'\0'.
Cheers,
Alex
>
> "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."
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-11 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:13 Issue in man page wcsncpy.3 Helge Kreutzmann
2023-03-11 23:23 ` Alejandro Colomar [this message]
2023-03-12 4:54 ` Helge Kreutzmann
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2022-12-04 9:07 Helge Kreutzmann
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
2022-12-04 23:28 ` Alejandro Colomar
2022-12-04 23:14 ` Alejandro Colomar
2022-12-04 20:44 ` Alejandro Colomar
2022-12-05 17:09 ` Helge Kreutzmann
2022-12-05 17:55 ` G. Branden Robinson
2023-01-25 20:01 ` Jakub Wilk
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=c36c21ee-8244-a6fe-7bfb-2f4a2b61c5fc@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.