Lines Matching refs:read
4 Simple filesystem read/write is achieved using the ``uv_fs_*`` functions and the
65 .. rubric:: uvcat/main.c - read callback
72 In the case of a read call, you should pass an *initialized* buffer which will
73 be filled with data before the read callback is triggered. The ``uv_fs_*``
87 simply drives the next read. Thus read and write proceed in lockstep via
121 same patterns as the read/write/open calls, returning the result in the
211 .. rubric:: uvtee/main.c - read on pipes
237 The read callback ``nread`` parameter is less than 0 on any error. This error
245 allocate memory. In this case, the read callback is invoked with error
246 UV_ENOBUFS. libuv will continue to attempt to read the stream though, so you
249 The read callback may be called with ``nread = 0``, indicating that at this
250 point there is nothing to be read. Most applications will just ignore this.
258 ``write_data()`` makes a copy of the buffer obtained from read. This buffer
