unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: Martin Sebor <msebor@redhat.com>
Subject: Re: [PATCH] mbstowcs: Document, test, and fix null pointer dst semantics.
Date: Fri, 22 May 2020 13:25:24 +0200	[thread overview]
Message-ID: <87r1vc43ff.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <63ea09de-e943-c26e-c821-093ba303d76b@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Thu, 21 May 2020 22:15:43 -0400")

* Carlos O'Donell via Libc-alpha:

> +If @var{wstring} is a null pointer then no output is written and the
> +conversion proceeds as above, and the result is returned. In practice
> +such behaviour is useful for calculating the exact number of wide
> +characters required to convert @var{string}.  This behaviour of accepting
> +a null pointer for @var{wstring} is an @w{XSI} extension to the requirements
> +in @w{ISO C} and @w{POSIX}.

If you refer standards here, these references should be framed in terms
of XPG etc., as in other places of the manual.

An easy way out (that doesn't need researching history here) would be to
declare this as a GNU extension.

Thanks,
Florian


  reply	other threads:[~2020-05-22 11:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  2:15 [PATCH] mbstowcs: Document, test, and fix null pointer dst semantics Carlos O'Donell via Libc-alpha
2020-05-22 11:25 ` Florian Weimer via Libc-alpha [this message]
2020-06-01 15:50   ` [PATCH v2] mbstowcs: Document, test, and fix null pointer dst semantics (Bug 25219) Carlos O'Donell via Libc-alpha
2020-06-01 16:17     ` Florian Weimer
2020-06-01 16:28       ` Carlos O'Donell via Libc-alpha
2020-06-01 16:35         ` Florian Weimer
2020-06-01 16:57           ` [PATCH v3] " Carlos O'Donell via Libc-alpha
2020-06-01 17:07             ` Florian Weimer
2020-06-01 17:11               ` Carlos O'Donell via Libc-alpha
2020-05-22 15:56 ` [PATCH] mbstowcs: Document, test, and fix null pointer dst semantics Martin Sebor via Libc-alpha
2020-05-22 16:15 ` Matheus Castanho via Libc-alpha
2020-05-22 16:35   ` Carlos O'Donell via Libc-alpha
2020-05-22 17:06     ` Florian Weimer via Libc-alpha
2020-05-25 14:10       ` Matheus Castanho via Libc-alpha
2020-06-01 13:40 ` Matheus Castanho via Libc-alpha
2020-06-01 15:11   ` Carlos O'Donell via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1vc43ff.fsf@oldenburg2.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=msebor@redhat.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 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).