Lines Matching refs:a
7 Some APIs changed quite a bit throughout the 1.0.0 development process. Here
8 is a migration guide for the most significant changes that happened after 0.10
16 allocated memory for a new loop and initialized it; and destroyed with `uv_loop_delete`,
46 Error handling had a major overhaul in libuv 1.0. In general, functions and status parameters
48 to fetch the error code, which was a positive number.
51 a negative number in case of error.
57 ... assume 'server' is a TCP server which is already listening
68 ... assume 'server' is a TCP server which is already listening
78 In libuv 0.10 Unix used a threadpool which defaulted to 4 threads, while Windows used the
79 `QueueUserWorkItem` API, which uses a Windows internal threadpool, which defaults to 512
90 In libuv 0.10 the callback had to return a filled :c:type:`uv_buf_t` by value:
98 In libuv 1.0 a pointer to a buffer is passed to the callback, which the user
112 libuv 1.0 unified the IPv4 and IPv6 APIS. There is no longer a `uv_tcp_bind` and `uv_tcp_bind6`
116 ``struct sockaddr_in6``. Now functions take a ``struct sockaddr*`` (note it's a pointer).
140 This change applies to all functions that made a distinction between IPv4 and IPv6
147 The streams and UDP data receive callbacks now get a pointer to a :c:type:`uv_buf_t` buffer,
148 not a structure by value.
191 data on a pipe, which could also result in the reception of handles over it. The callback
221 Extracting the file descriptor out of a handle
225 order to get access to the file descriptor of a TCP handle, for example.
237 `uv_fs_readdir` returned a list of strings in the `req->ptr` field upon completion in
241 In addition, instead of allocating a full list strings, the user is able to get one
242 result at a time by using the :c:func:`uv_fs_scandir_next` function. This function
243 does not need to make a roundtrip to the threadpool, because libuv will keep the
