unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	Martin Sebor <msebor@redhat.com>,
	Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] mbstowcs: Document, test, and fix null pointer dst semantics (Bug 25219)
Date: Mon, 01 Jun 2020 18:35:44 +0200	[thread overview]
Message-ID: <87a71myc9r.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <66774998-1f2c-82d3-237e-914e950edd4f@redhat.com> (Carlos O'Donell's message of "Mon, 1 Jun 2020 12:28:20 -0400")

* Carlos O'Donell:

> How about this?
> ~~~
> This behaviour of accepting a null pointer for @var{wstring} is an @w{XPG4.2}
> extension that is not specified in @w{ISO C} and is optional in @w{POSIX}.
> ~~~

Looks good to me.

  reply	other threads:[~2020-06-01 16:35 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
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 [this message]
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=87a71myc9r.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --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).