On Fri, 23 Jun 2000, Bohne, Peter wrote: > Anytime you make a call that can potentially set errno, and you are planning > to *check* errno afterwards, you have to set errno to 0 yourself. Once a ...but you would only be checking errno if the call failed and if the call failed then it will have set errno. Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- RE: libc_r/_read(), should the errno be reset to 0? Bohne, Peter
- RE: libc_r/_read(), should the errno be reset to 0? andrew
- RE: libc_r/_read(), should the errno be reset to 0? FengYue
- RE: libc_r/_read(), should the errno be reset to 0? Bohne, Peter
- RE: libc_r/_read(), should the errno be reset to 0? Bohne, Peter
- RE: libc_r/_read(), should the errno be reset to 0? Bohne, Peter
- RE: libc_r/_read(), should the errno be reset t... Chuck Robey
- RE: libc_r/_read(), should the errno be res... Garance A Drosihn
- RE: libc_r/_read(), should the errno be... Chuck Robey
- RE: libc_r/_read(), should the err... Garance A Drosihn
- RE: libc_r/_read(), should the errno be reset to 0? Bohne, Peter