On Wed, Dec 23, 2015 at 9:27 AM, Ingo Schwarze wrote:
> i just noticed a bug in fgetwc(3) in our libc, the function used to
> implement getwc(3), getwchar(3), getws(3), getwln(3) and the wscanf(3)
> family of functions. In case of an encoding error, it does not set
> the error indicator, such tha
Ingo Schwarze writes:
> Hi,
>
> i just noticed a bug in fgetwc(3) in our libc, the function used to
> implement getwc(3), getwchar(3), getws(3), getwln(3) and the wscanf(3)
> family of functions. In case of an encoding error, it does not set
> the error indicator, such that a program correctly c
Hi,
i just noticed a bug in fgetwc(3) in our libc, the function used to
implement getwc(3), getwchar(3), getws(3), getwln(3) and the wscanf(3)
family of functions. In case of an encoding error, it does not set
the error indicator, such that a program correctly checking ferror(3)
after WEOF may mi