From: Charles Nutter Date: 2012-03-16T13:06:35+09:00 Subject: [ruby-core:43327] [ruby-trunk - Feature #5138] Add nonblocking IO that does not use exceptions for EOF and EWOULDBLOCK Issue #5138 has been updated by Charles Nutter. Related: http://bugs.ruby-lang.org/issues/6154 ---------------------------------------- Feature #5138: Add nonblocking IO that does not use exceptions for EOF and EWOULDBLOCK https://bugs.ruby-lang.org/issues/5138#change-24632 Author: Yehuda Katz Status: Open Priority: Normal Assignee: Yukihiro Matsumoto Category: core Target version: 1.9.4 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/