On Fri, 23 Jun 2000, Bohne, Peter wrote: > This means that *you* should set errno to 0 just before you do the read > call. At this point, you no longer care what it had been before. Why set it at all? If read returns an error then it will set it for you and if read doesn't return an error it doesn't really matter whats in errno. Am I missing something? 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