elm 2.5.3 and glibc 2.1.93
Andreas Schwab
schwab@suse.de
Mon Sep 25 01:20:00 GMT 2000
"H . J . Lu" <hjl@lucon.org> writes:
|> On Sat, Sep 23, 2000 at 06:37:18PM +0200, Mark Kettenis wrote:
|> > My copy of the manual says that:
|> >
|> > ... you should not use `errno' to determine _whether_ a call
|> > failed. The proper way to do that is documented for each
|> > function. _If_ the call the failed, you can examine `errno'.
|> >
|>
|> Read my code again. It does just that. It only assumes errno is
|> unchanged when bar () returns 0 since glibc manual says so.
And this is what is _broken_, and always has been.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
More information about the Libc-hacker
mailing list