From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 28276 invoked from network); 20 Mar 2023 20:23:20 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 20 Mar 2023 20:23:20 -0000
Received: (qmail 24021 invoked by uid 550); 20 Mar 2023 20:23:17 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 23982 invoked from network); 20 Mar 2023 20:23:16 -0000
Date: Mon, 20 Mar 2023 16:23:04 -0400
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: =?utf-8?B?SuKCkeKCmeKCmw==?= Gustedt <jens.gustedt@inria.fr>
Message-ID: <20230320202302.GT4163@brightrain.aerifal.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [musl] WG14 hasn't fixed the ferror status issue for fputwc EILSEQ yet?

The issue for fgetwc has been fixed according to the discussion here:

https://austingroupbugs.net/view.php?id=1022

and indeed is fixed in the C2x draft. But the corresponding issue for
fputwc is not fixed. POSIX still requires setting the error indicator
for the stream on EILSEQ, but ISO C (by omission/accident) disallows
it.

Any chance we can get this fixed in time for C2x release?

I noticed it while fixing the wide printf error handling bugs in musl
(reported by Bruno), while trying to confirm that it's correct to rely
on the error status being set.

Rich