ruby-changes:8187
From: akr <ko1@a...>
Date: Wed, 8 Oct 2008 19:07:24 +0900 (JST)
Subject: [ruby-changes:8187] Ruby:r19715 (trunk): rdoc update.
akr 2008-10-08 19:06:16 +0900 (Wed, 08 Oct 2008) New Revision: 19715 http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=rev&revision=19715 Log: rdoc update. Modified files: trunk/io.c Index: io.c =================================================================== --- io.c (revision 19714) +++ io.c (revision 19715) @@ -1760,10 +1760,10 @@ * Note that readpartial behaves similar to sysread. * The differences are: * * If the buffer is not empty, read from the buffer instead of "sysread for buffered IO (IOError)". - * * It doesn't cause Errno::EAGAIN and Errno::EINTR. When readpartial meets EAGAIN and EINTR by read system call, readpartial retry the system call. + * * It doesn't cause Errno::EWOULDBLOCK and Errno::EINTR. When readpartial meets EWOULDBLOCK and EINTR by read system call, readpartial retry the system call. * * The later means that readpartial is nonblocking-flag insensitive. - * It blocks on the situation IO#sysread causes Errno::EAGAIN as if the fd is blocking mode. + * It blocks on the situation IO#sysread causes Errno::EWOULDBLOCK as if the fd is blocking mode. * */ @@ -1792,7 +1792,7 @@ * it must reference a String, which will receive the data. * * read_nonblock just calls read(2). - * It causes all errors read(2) causes: EAGAIN, EINTR, etc. + * It causes all errors read(2) causes: Errno::EWOULDBLOCK, Errno::EINTR, etc. * The caller should care such errors. * * read_nonblock causes EOFError on EOF. @@ -1826,7 +1826,7 @@ * It returns the number of bytes written. * * write_nonblock just calls write(2). - * It causes all errors write(2) causes: EAGAIN, EINTR, etc. + * It causes all errors write(2) causes: Errno::EWOULDBLOCK, Errno::EINTR, etc. * The result may also be smaller than string.length (partial write). * The caller should care such errors and partial write. * -- ML: ruby-changes@q... Info: http://www.atdot.net/~ko1/quickml/