public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Andriy Utkin <andriy_utkin@fastmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] mbsrtowcs.3: add a note for conversion completion
Date: Tue, 14 Nov 2023 10:21:27 +0100	[thread overview]
Message-ID: <ZVM8Hzfw9CCRHWwR@debian> (raw)
In-Reply-To: <20231113134857.1639387-1-andriy_utkin@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 2717 bytes --]

Hello Andriy,

On Mon, Nov 13, 2023 at 01:48:57PM +0000, Andriy Utkin wrote:
> This adds a note to resolve a confusion I had.
> Maintainers are most welcome to improve my wording.
> 
> I aimed for this function to work in such a manner so that
> it would convert the entire string. So I allocated a destination buffer
> to accommodate the string length in wide charaters and the terminating
> null. The function was called with len equal to the length of the string
> in wide characters, as returned by mbsrtowcs(NULL, ...).
> 
> This resulted in *src being updated to point at the trailing null
> character, rather than NULL which I expected.
> 
> Here is an example which illustrates the point:
> 
> Code:
> 
>     #include <wchar.h>
>     #include <stdio.h>
>     int main(void) {
>         const char *src = "Hello", *s1 = src, *s2 = src;
>         wchar_t dest[6];
>         int ret;
>         printf("src is %p\n", src);
>         ret = mbsrtowcs(NULL, &src, 0, NULL);
>         printf("mbsrtowcs(src=NULL) returned %d\n", ret);
>         ret = mbsrtowcs(dest, &s1, 5, NULL);
>         printf("mbsrtowcs(len=5) returned %d, updated src is %p\n", ret, s1);
>         ret = mbsrtowcs(dest, &s2, 6, NULL);
>         printf("mbsrtowcs(len=6) returned %d, updated src is %p\n", ret, s2);
>         return 0;
>     }
> 
> Output:
> 
>     src is 0x402010
>     mbsrtowcs(src=NULL) returned 5
>     mbsrtowcs(len=5) returned 5, updated src is 0x402015
>     mbsrtowcs(len=6) returned 5, updated src is (nil)

mbstowcs(3) has the following:

     In  order  to  avoid the case 2 above, the programmer should make
     sure n is greater than or equal to mbstowcs(NULL,src,0)+1.

We could add that.  BTW, maybe you want to use mbstowcs(3), which is
simpler.  I think we could add something saying that mbsrtowcs(3) is a
restartable version of mbstowcs(3).

Thanks,
Alex

> ---
>  man3/mbsrtowcs.3 | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/man3/mbsrtowcs.3 b/man3/mbsrtowcs.3
> index 11741d187..4718b335d 100644
> --- a/man3/mbsrtowcs.3
> +++ b/man3/mbsrtowcs.3
> @@ -155,6 +155,15 @@ current locale.
>  Passing NULL as
>  .I ps
>  is not multithread safe.
> +.P
> +Calling this function with
> +.I len
> +set to the value returned from
> +.I mbsrtowcs(NULL, ...)
> +behaves according to scenario #2 described above:
> +.I *src
> +is set to the address of the terminating null wide character, rather than to NULL.
> +Add 1 to that value for it to work according to scenario #3 (complete conversion).
>  .SH SEE ALSO
>  .BR iconv (3),
>  .BR mbrtowc (3),
> -- 
> 2.41.0
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-11-14  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 13:48 [PATCH] mbsrtowcs.3: add a note for conversion completion Andriy Utkin
2023-11-14  9:21 ` Alejandro Colomar [this message]
2023-11-14  9:47   ` Andriy Utkin
2023-11-14 10:04     ` 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=ZVM8Hzfw9CCRHWwR@debian \
    --to=alx@kernel.org \
    --cc=andriy_utkin@fastmail.com \
    --cc=linux-man@vger.kernel.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