From: "headius (Charles Nutter)" Date: 2013-09-27T20:14:11+09:00 Subject: [ruby-core:57433] [ruby-trunk - Feature #5138] Add nonblocking IO that does not use exceptions for EOF and EWOULDBLOCK Issue #5138 has been updated by headius (Charles Nutter). Hah... I was just stopping by to suggest the keyword argument as a compromise form...and it turns out that's exactly what we went with. Excellent! ---------------------------------------- Feature #5138: Add nonblocking IO that does not use exceptions for EOF and EWOULDBLOCK https://bugs.ruby-lang.org/issues/5138#change-42039 Author: wycats (Yehuda Katz) Status: Closed Priority: Normal Assignee: tenderlovemaking (Aaron Patterson) Category: core Target version: next minor The current Ruby I/O classes have non-blocking methods (read_nonblock and write_nonblock). These methods will never block, and if they would block, they raise an exception instead (IO::WaitReadable or IO::WaitWritable). In addition, if the IO is at EOF, they raise an EOFError. These exceptions are raised repeatedly in virtually every use of the non-blocking methods. This patch adds a pair of methods (try_read_nonblock and try_write_nonblock) that have the same semantics as the existing methods, but they return Symbols instead of raising exceptions for these routine cases: * :read_would_block * :write_would_block * :eof The patch contains updates for IO, StringIO, and OpenSSL. The updates are fully documented and tested. -- http://bugs.ruby-lang.org/