Right - but unless I'm mis-remembering the original post (which I may well
be), your *second* read() succeeded, but errno was still set to EAGAIN,
which was causing you some sort of headache. My apologies if I've got my
memory mixed up - happens all the time :-)
pete
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 23, 2000 10:25 AM
> To: Bohne, Peter
> Cc: FengYue; [EMAIL PROTECTED]
> Subject: RE: libc_r/_read(), should the errno be reset to 0?
>
>
>
>
> 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
