apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <dr...@jetnet.co.uk>
Subject Re: EGAIN, EINTR et.al.
Date Mon, 29 Oct 2001 23:25:25 GMT
> Right now we are trapping EACCESS and moving it to 'EAGAIN' for a flock().
> But on some platforms you can get things like EWOULDBLOCK and EINTR too.
> In APR is there a convenient macro to figure out if the exit code is a
> 'hard' error (say EINVAL, EBADF, ENOTSUPP) or one to figure out if it is
> a retryable type error ?

Don't think we have one, but it may not be a bad idea as we could wrap up
the platform differences nicely and make our code more readable...

Only thing is would we need a lot of basically identical macro's just for
different calls (sockets, files, flocks and so on).  Worth a look.


View raw message