Skip to content
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

Handle EAGAIN errors on socket operations #2611

Merged
merged 1 commit into from
Mar 28, 2018

Conversation

dipinhora
Copy link
Contributor

According to man pages for write/read/send/etc, POSIX allows
for operations on nonblocking sockets to fail with either
EWOULDBLOCK or EAGAIN.

This commit updates the code in socket.c to handle EAGAIN
the same as EWOULDBLOCK for increased portability.

According to man pages for write/read/send/etc, POSIX allows
for operations on nonblocking sockets to fail with either
EWOULDBLOCK or EAGAIN.

This commit updates the code in socket.c to handle EAGAIN
the same as EWOULDBLOCK for increased portability.
@jemc jemc added the changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge label Mar 28, 2018
@jemc jemc merged commit ce1fd4f into ponylang:master Mar 28, 2018
ponylang-main added a commit that referenced this pull request Mar 28, 2018
dipinhora added a commit to dipinhora/ponyc that referenced this pull request Jun 5, 2018
According to man pages for write/read/send/etc, POSIX allows
for operations on nonblocking sockets to fail with either
EWOULDBLOCK or EAGAIN.

This commit updates the code in socket.c to handle EAGAIN
the same as EWOULDBLOCK for increased portability.
dipinhora pushed a commit to dipinhora/ponyc that referenced this pull request Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants