Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c1a5d6ff-c6e4-0238-7577-8d1a9689d6bb@gmail.com>
Date: Mon, 20 Mar 2023 21:26:22 +0100
From: Gabriel Ravier <gabravier@...il.com>
To: musl@...ts.openwall.com, Rich Felker <dalias@...c.org>
Cc: Jā‚‘ā‚™ā‚› Gustedt <jens.gustedt@...ia.fr>
Subject: Re: WG14 hasn't fixed the ferror status issue for fputwc
 EILSEQ yet?

On 3/20/23 21:23, Rich Felker wrote:
> 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

A Defect Report to that effect can probably get in later pretty quickly 
(by WG14 standards) but IIRC unless I'm wrong about how WG14 works I'm 
pretty sure new proposals not directly related to national body comments 
are not gonna get into C2x (and C2x national body comments have already 
been made).

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.