/libuv/docs/src/ |
H A D | udp.rst | 197 :c:func:`uv_udp_init`. 231 :c:func:`uv_udp_init`. 280 :c:func:`uv_udp_init`. 295 :c:func:`uv_udp_init`. 317 implicitly with :c:func:`uv_udp_send()` or :c:func:`uv_udp_recv_start`. 330 implicitly with :c:func:`uv_udp_send()` or :c:func:`uv_udp_recv_start`. 343 implicitly with :c:func:`uv_udp_send()` or :c:func:`uv_udp_recv_start`. 356 implicitly with :c:func:`uv_udp_send()` or :c:func:`uv_udp_recv_start`. 369 implicitly with :c:func:`uv_udp_send()` or :c:func:`uv_udp_recv_start`. 394 :c:func:`uv_udp_init`. [all …]
|
H A D | async.rst | 20 Type definition for callback passed to :c:func:`uv_async_init`. 54 …:c:func:`uv_async_send` is `async-signal-safe <https://man7.org/linux/man-pages/man7/signal-safety… 58 libuv will coalesce calls to :c:func:`uv_async_send`, that is, not every call to it will 59 yield an execution of the callback. For example: if :c:func:`uv_async_send` is called 5 61 :c:func:`uv_async_send` is called again after the callback was called, it will be called
|
H A D | loop.rst | 22 See :c:func:`uv_loop_configure`. 34 Mode used to run the loop with :c:func:`uv_run`. 46 Type definition for callback passed to :c:func:`uv_walk`. 70 first call to :c:func:`uv_run` unless mentioned otherwise. 78 second argument to :c:func:`uv_loop_configure` is the signal number. 87 This option is necessary to use :c:func:`uv_metrics_idle_time`. 123 referenced handles or requests. Returns non-zero if :c:func:`uv_stop` 144 Stop the event loop, causing :c:func:`uv_run` to end as soon as 183 Use :c:func:`uv_hrtime` if you need sub-millisecond granularity. 213 before calling :c:func:`uv_run` or any other API function using [all …]
|
H A D | migration_010_100.rst | 39 Error handling was omitted for brevity. Check the documentation for :c:func:`uv_loop_init` 40 and :c:func:`uv_loop_close`. 113 duality, there is only :c:func:`uv_tcp_bind` now. 136 The IPv4 and IPv6 struct creating functions (:c:func:`uv_ip4_addr` and :c:func:`uv_ip6_addr`) 204 handles using :c:func:`uv_pipe_pending_count` and :c:func:`uv_pipe_pending_type` while in 231 This is now properly exposed through the :c:func:`uv_fileno` function. 238 libuv 0.10. In 1.0, this function got renamed to :c:func:`uv_fs_scandir`, since it's 242 result at a time by using the :c:func:`uv_fs_scandir_next` function. This function
|
H A D | threadpool.rst | 21 function makes use of the threadpool (i.e. when using :c:func:`uv_queue_work`) 40 Callback passed to :c:func:`uv_queue_work` which will be run on the thread 45 Callback passed to :c:func:`uv_queue_work` which will be called on the loop 47 was cancelled using :c:func:`uv_cancel` `status` will be ``UV_ECANCELED``. 70 This request can be cancelled with :c:func:`uv_cancel`.
|
H A D | tcp.rst | 21 Flags used in :c:func:`uv_tcp_bind`. 62 just like :c:func:`uv_tcp_init`. 109 error from :c:func:`uv_listen` or :c:func:`uv_tcp_connect` unless you specify 111 call to this function does not guarantee that the call to :c:func:`uv_listen` or 112 :c:func:`uv_tcp_connect` will succeed as well. 114 :param handle: TCP handle. It should have been initialized with :c:func:`uv_tcp_init`. 169 then calling :c:func:`uv_close`. 170 Due to some platform inconsistencies, mixing of :c:func:`uv_shutdown` and 171 :c:func:`uv_tcp_close_reset` calls is not allowed.
|
H A D | poll.rst | 28 closed immediately after a call to :c:func:`uv_poll_stop` or :c:func:`uv_close`. 46 Type definition for callback passed to :c:func:`uv_poll_start`. 82 to :c:func:`uv_poll_init`. On windows it takes a SOCKET handle. 106 then call :c:func:`uv_close` on the handle. 109 Calling :c:func:`uv_poll_start` on a handle that is already active is 130 :c:func:`uv_poll_start` on a poll handle associated with this socket, 146 Calling :c:func:`uv_poll_stop` is effective immediately: any pending
|
H A D | stream.rst | 49 by calling :c:func:`uv_read_stop` or :c:func:`uv_close`. Trying to read 63 Callback called after a connection started by :c:func:`uv_connect` is done. 74 The user can accept the connection by calling :c:func:`uv_accept`. 123 This call is used in conjunction with :c:func:`uv_listen` to accept incoming 140 :c:func:`uv_read_stop` is called. 142 .. versionchanged:: 1.38.0 :c:func:`uv_read_start()` now consistently 188 This also holds for :c:func:`uv_write2`. 202 Same as :c:func:`uv_write`, but won't queue a write request if it can't be 213 Same as :c:func:`uv_try_write` and extended write function for sending 214 handles over a pipe like c:func:`uv_write2`.
|
H A D | threading.rst | 21 value that was passed to :c:func:`uv_thread_create`. 60 Options for spawning a new thread (passed to :c:func:`uv_thread_create_ex`). 91 Like :c:func:`uv_thread_create`, but additionally specifies options for creating a new thread. 110 and must be greater-than-or-equal-to :c:func:`uv_cpumask_size`. 123 and must be greater-than-or-equal-to :c:func:`uv_cpumask_size`. 190 Runs a function once and only once. Concurrent calls to :c:func:`uv_once` with the 243 1. Callers should be prepared to deal with spurious wakeups on :c:func:`uv_cond_wait` 244 and :c:func:`uv_cond_timedwait`. 245 2. The timeout parameter for :c:func:`uv_cond_timedwait` is relative to the time 247 3. On z/OS, the timeout parameter for :c:func:`uv_cond_timedwait` is converted to an [all …]
|
H A D | timer.rst | 13 right after waking up from waiting for I/O. See also :c:func:`uv_update_time`. 28 Type definition for callback passed to :c:func:`uv_timer_start`. 55 …Does not update the event loop's concept of "now". See :c:func:`uv_update_time` for more informati… 88 :c:func:`uv_now()`.
|
H A D | misc.rst | 32 See :c:func:`uv_replace_allocator`. 37 See :c:func:`uv_replace_allocator`. 42 See :c:func:`uv_replace_allocator`. 47 See :c:func:`uv_replace_allocator`. 53 :c:func:`uv_random`. 110 Clock source for :c:func:`uv_clock_gettime`. 419 :c:func:`uv_interface_addresses`. 577 :c:func:`uv_os_free_passwd`. 589 :c:func:`uv_os_free_passwd`. 600 :c:func:`uv_os_free_group`. [all …]
|
H A D | handle.rst | 57 Type definition for callback passed to :c:func:`uv_read_start` and 58 :c:func:`uv_udp_recv_start`. The user must allocate memory and fill the supplied 85 Type definition for callback passed to :c:func:`uv_close`. 279 by unreferencing handles which are active, for example by calling :c:func:`uv_unref` 280 after calling :c:func:`uv_timer_start`. 285 All handles are referenced when active by default, see :c:func:`uv_is_active`
|
H A D | pipe.rst | 59 unlike :c:func:`uv_pipe_bind2`. 89 unlike :c:func:`uv_pipe_connect2`. 151 First - call :c:func:`uv_pipe_pending_count`, if it's > 0 then initialize 152 a handle of the given `type`, returned by :c:func:`uv_pipe_pending_type`
|
H A D | fs.rst | 120 Used in :c:func:`uv_fs_statfs`. 156 Used in :c:func:`uv_fs_scandir_next`. 168 Used by :c:func:`uv_fs_opendir()`, :c:func:`uv_fs_readdir()`, and 169 :c:func:`uv_fs_closedir()`. `dirents` represents a user provided array of 204 as :c:func:`uv_fs_read` or :c:func:`uv_fs_write` it indicates the amount of 209 Stores the result of :c:func:`uv_fs_stat` and other stat requests. 213 Stores the result of :c:func:`uv_fs_readlink` and 214 :c:func:`uv_fs_realpath` and serves as an alias to `statbuf`. 334 for the request is called, the user can use :c:func:`uv_fs_scandir_next` to 393 :c:func:`uv_fs_sendfile()` is used.
|
H A D | design.rst | 86 * If the loop is going to be stopped (:c:func:`uv_stop` was called), the timeout is 0. 100 #. Close callbacks are called. If a handle was closed by calling :c:func:`uv_close` it will 110 iteration ends and :c:func:`uv_run` will return. If the loop was run with ``UV_RUN_DEFAULT`` 137 * User specified code via :c:func:`uv_queue_work`
|
H A D | dll.rst | 31 -1 on error. Call :c:func:`uv_dlerror` to get the error message.
|
H A D | process.rst | 20 Options for spawning the process (passed to :c:func:`uv_spawn`. 175 The PID of the spawned process. It's set after calling :c:func:`uv_spawn`. 205 Various flags that control how :c:func:`uv_spawn` behaves. See 227 This is not supported on Windows, :c:func:`uv_spawn` will fail and set the error
|
H A D | signal.rst | 66 Type definition for callback passed to :c:func:`uv_signal_start`. 94 Same functionality as :c:func:`uv_signal_start` but the signal handler is reset the moment
|
H A D | dns.rst | 45 with :c:func:`uv_freeaddrinfo`. 88 Call :c:func:`uv_freeaddrinfo` to free the addrinfo structure.
|
H A D | prepare.rst | 20 Type definition for callback passed to :c:func:`uv_prepare_start`.
|
H A D | check.rst | 20 Type definition for callback passed to :c:func:`uv_check_start`.
|
H A D | idle.rst | 28 Type definition for callback passed to :c:func:`uv_idle_start`.
|
H A D | fs_event.rst | 41 Callback passed to :c:func:`uv_fs_event_start` which will be called repeatedly 68 Flags that can be passed to :c:func:`uv_fs_event_start` to control its
|
/libuv/src/unix/ |
H A D | pipe.c | 349 uv__peersockfunc func, in uv__pipe_getsockpeername() argument 369 func, in uv__pipe_getsockpeername()
|
/libuv/src/win/ |
H A D | core.c | 663 uv__peersockfunc func, in uv__getsockpeername() argument 678 result = func((SOCKET) fd, name, namelen); in uv__getsockpeername()
|