On 18/11/2014, Louis Santillan <lpsan...@gmail.com> wrote: > Returning error code doesn't work well for many asynchronous calls (aio_*) > [0].
Why? aio_error indeed returns an error code, and separate aio_return and aio_error would not even be needed if read, write, etc returned as I proposed, as one call could so return: • EINPROGRESS: not yet complete • ECANCELED: canceled • other: return value of synchronous operation
