Skip to content

use EWOULDBLOCK additionally on all places where EAGAIN is used #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 20, 2017
Merged

use EWOULDBLOCK additionally on all places where EAGAIN is used #24

merged 1 commit into from
Feb 20, 2017

Conversation

noxxi
Copy link

@noxxi noxxi commented Feb 19, 2017

This is a continuation of #11 because my attempt to rebase the 2 year old pull request resulted in a mess. Note that the major part of the orginal pull request was already fixed and this new pull request adds a fix on a place where EAGAIN or EWOULDBLOCK would probably not happen anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants