Re: fgetwln(3) fails to report most encoding errors

2016-08-21 Thread Jeremie Courreges-Anglas
Ingo Schwarze writes: > Hi, > > did i mention already that libc wide character code is buggy as hell? > I looked at another very simple function of only 30 lines of code > and promptly found another bug. > > The fgetwln(3) manual is quite explicit that the "fgetwln() function > may also fail ...

fgetwln(3) fails to report most encoding errors

2016-08-21 Thread Ingo Schwarze
Hi, did i mention already that libc wide character code is buggy as hell? I looked at another very simple function of only 30 lines of code and promptly found another bug. The fgetwln(3) manual is quite explicit that the "fgetwln() function may also fail ... for any of the errors specified for ..