From: "shyouhei (Shyouhei Urabe)" Date: 2022-06-29T06:09:29+00:00 Subject: [ruby-core:109089] [Ruby master Bug#18881] IO#read_nonblock raises IOError when called following buffered character IO Issue #18881 has been updated by shyouhei (Shyouhei Urabe). nobu (Nobuyoshi Nakada) wrote in #note-4: > @shyouhei Even without any conversion? Yes. "Byte oriented and character oriented IO operations cannot be mixed at all" sounds much simpler than the current (it sometimes raises and sometimes doesn't). ---------------------------------------- Bug #18881: IO#read_nonblock raises IOError when called following buffered character IO https://bugs.ruby-lang.org/issues/18881#change-98235 * Author: javanthropus (Jeremy Bopp) * Status: Rejected * Priority: Normal * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x64-mingw-ucrt] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- The following example code works as expected on Linux but raises an `IOError` on Windows: ``` ruby r, w = IO.pipe w.write("foobar") c = r.getc r.ungetc(c) r.read_nonblock(3) ``` The error message is: ``` IOError: byte oriented read for character buffered IO ``` -- https://bugs.ruby-lang.org/ Unsubscribe: