/libuv/src/unix/ |
H A D | fsevents.c | 672 uv__cf_loop_signal_t* s; in uv__fsevents_loop_delete() local 689 s = uv__queue_data(q, uv__cf_loop_signal_t, member); in uv__fsevents_loop_delete() 691 uv__free(s); in uv__fsevents_loop_delete() 736 uv__cf_loop_signal_t* s; in uv__cf_loop_cb() local 749 s = uv__queue_data(item, uv__cf_loop_signal_t, member); in uv__cf_loop_cb() 752 if (s->handle == NULL) in uv__cf_loop_cb() 755 uv__fsevents_reschedule(state, loop, s->type); in uv__cf_loop_cb() 757 uv__free(s); in uv__cf_loop_cb()
|
H A D | darwin-proctitle.c | 109 #define S(s) pCFStringCreateWithCString(NULL, (s), kCFStringEncodingUTF8) in uv__set_process_title()
|
H A D | pipe.c | 34 static int includes_nul(const char *s, size_t n) { in includes_nul() argument 39 s++; in includes_nul() 42 return NULL != memchr(s, '\0', n); in includes_nul()
|
H A D | aix.c | 892 char* s; in uv_setup_args() local 928 s = (char*) &new_argv[argc + 1]; in uv_setup_args() 931 memcpy(s, argv[i], size); in uv_setup_args() 932 new_argv[i] = s; in uv_setup_args() 933 s += size; in uv_setup_args()
|
/libuv/src/ |
H A D | strscpy.h | 37 ssize_t uv__strscpy(char* d, const char* s, size_t n);
|
H A D | idna.h | 29 ssize_t uv__idna_toascii(const char* s, const char* se, char* d, char* de);
|
H A D | uv-common.c | 55 char* uv__strdup(const char* s) { in uv__strdup() argument 56 size_t len = strlen(s) + 1; in uv__strdup() 60 return memcpy(m, s, len); in uv__strdup() 63 char* uv__strndup(const char* s, size_t n) { in uv__strndup() argument 65 size_t len = strlen(s); in uv__strndup() 72 return memcpy(m, s, len); in uv__strndup()
|
H A D | uv-common.h | 379 char *uv__strdup(const char* s); 380 char *uv__strndup(const char* s, size_t n);
|
/libuv/docs/src/ |
H A D | design.rst | 7 libuv is cross-platform support library which was originally written for `Node.js`_. It's designed 44 operations, and it's meant to be tied to a single thread. One can run multiple event loops 66 for a time before the loop's concept of *now* get their callbacks called. 70 requests or closing handles it's considered to be *alive*. 111 it will continue from the start if it's still *alive*, otherwise it will also end. 116 network I/O is **always** performed in a single thread, each loop's thread.
|
H A D | process.rst | 68 * parent's event loop alive unless the parent process calls uv_unref() on 69 * the child's process handle. 91 * uv_process_options_t's file field, has a directory component, 140 * The child process will be given a duplicate of the parent's 146 * The child process will be given a duplicate of the parent's 175 The PID of the spawned process. It's set after calling :c:func:`uv_spawn`.
|
H A D | pipe.rst | 52 it's required that it represents a valid pipe. 119 of the buffer and it's set to the number of bytes written to the buffer on 132 of the buffer and it's set to the number of bytes written to the buffer on 151 First - call :c:func:`uv_pipe_pending_count`, if it's > 0 then initialize
|
H A D | handle.rst | 59 :c:type:`uv_buf_t` structure. If NULL is assigned as the buffer's base or 0 as its length, 66 A suggested size (65536 at the moment in most cases) is provided, but it's just an indication, 117 Returns non-zero if the handle is active, zero if it's inactive. What 131 function, then it's active from the moment that function is called. 236 Be very careful when using this function. libuv assumes it's in control of the file
|
H A D | loop.rst | 7 The event loop is the central part of libuv's functionality. It takes care 160 poll in one thread and run the event loop's callbacks in another see 164 Embedding a kqueue fd in another kqueue pollset doesn't work on all platforms. It's not 187 Update the event loop's concept of "now". Libuv caches the current time
|
H A D | index.rst | 9 was primarily developed for use by `Node.js`_, but it's also used by `Luvit`_,
|
H A D | threading.rst | 93 Sets the specified thread's affinity to cpumask, which is specified in 111 Gets the specified thread's affinity setting. On Unix, this maps the 166 same guard will block all callers except one (it's unspecified which one).
|
/libuv/docs/src/guide/ |
H A D | introduction.rst | 37 from the browser. Using Google's V8_ and Marc Lehmann's libev_, node.js 47 library for system programming. Users outside of node.js include Mozilla's
|
H A D | networking.rst | 55 ``uv_listen`` is where we return to libuv's callback style. The second 77 Where you do bind/listen/accept on the server, on the client side it's simply 145 the OS will discard the data that could not fit* (That's UDP for you!). 195 perform normal socket operations on the retrieved addresses. Let's connect to 212 addrinfo(s)``. This also demonstrates ``uv_tcp_connect``. It is necessary to 229 Information about the system's network interfaces can be obtained through libuv
|
H A D | basics.rst | 58 This fits in well with libuv's event-loop approach, since the operating system 73 libuv's event loop is explained in more detail in the `documentation 85 With the basics out of the way, let's write our first libuv program. It does 205 implemented in the callback. For example, an IO watcher's callback will receive
|
H A D | threads.rst | 15 implementation and POSIX's :man:`pthreads(7)`. libuv's thread API is analogous to 18 A notable aspect of libuv's thread facilities is that it is a self contained 25 libuv's thread API is also very limited since the semantics and syntax of 251 Let's modify the fibonacci example to demonstrate ``uv_cancel()``. We first set
|
/libuv/test/ |
H A D | benchmark-pump.c | 277 static void connection_cb(uv_stream_t* s, int status) { in connection_cb() argument 281 ASSERT_PTR_EQ(server, s); in connection_cb() 294 r = uv_accept(s, stream); in connection_cb()
|
H A D | task.h | 228 ASSERT_BASE_LEN(memcmp(a, b, size) == 0, a, ==, b, s, size) 231 ASSERT_BASE_LEN(memcmp(a, b, size) != 0, a, !=, b, s, size)
|
/libuv/ |
H A D | .mailmap | 52 Saúl Ibarra Corretgé <s@saghul.net> 53 Saúl Ibarra Corretgé <s@saghul.net> <saghul@gmail.com>
|
H A D | SECURITY.md | 13 If you believe you have found a security vulnerability in `libuv`, please use the [GitHub's private…
|
H A D | CONTRIBUTING.md | 46 Please adhere to libuv's code style. In general it follows the conventions from 143 - `CMakeLists.txt`: add the file's name to the `uv_test_sources` list. 144 - `Makefile.am`: add the file's name to the `test_run_tests_SOURCES` list.
|
H A D | README.md | 6 was primarily developed for use by [Node.js][], but it's also 140 Git tags are signed with the developer's key, they can be verified as follows: 253 $ env UV_TEST_TIMEOUT_MULTIPLIER=2 build/uv_run_tests # 10s instead of 5s
|