Searched refs:part (Results 1 – 11 of 11) sorted by relevance
| /libuv/test/ |
| H A D | runner-win.c | 73 int process_start(char *name, char *part, process_info_t *p, int is_helper) { in process_start() argument
125 if (part) { in process_start()
131 part) < 0) { in process_start()
163 p->name = part; in process_start()
|
| H A D | runner.h | 117 int run_test_part(const char* test, const char* part);
139 int process_start(char *name, char* part, process_info_t *p, int is_helper);
|
| H A D | runner.c | 351 int run_test_part(const char* test, const char* part) { in run_test_part() argument
357 strcmp(part, task->process_name) == 0) { in run_test_part()
363 fprintf(stdout, "No test part with that name: %s:%s\n", test, part); in run_test_part()
|
| H A D | runner-unix.c | 85 int process_start(char* name, char* part, process_info_t* p, int is_helper) { in process_start() argument
112 args[n++] = part; in process_start()
|
| /libuv/docs/src/ |
| H A D | design.rst | 43 The I/O (or event) loop is the central part of libuv. It establishes the content for all I/O
51 on Windows. As part of a loop iteration the loop will block waiting for I/O activity on sockets
73 most part. There are cases, however, in which calling such a callback is deferred for the next
|
| H A D | loop.rst | 7 The event loop is the central part of libuv's functionality. It takes care
|
| /libuv/docs/src/guide/ |
| H A D | introduction.rst | 55 All the example code and the source of the book is included as part of
|
| H A D | filesystem.rst | 80 one-off, or are done as part of the startup or shutdown stage are performed
|
| H A D | utilities.rst | 427 *2* J Clear part of the screen, 2 is entire screen
|
| /libuv/ |
| H A D | LICENSE-docs | 22 exhaustive, and do not form part of our licenses.
143 in part; and
392 the avoidance of doubt, this paragraph does not form part of the
|
| H A D | CMakeLists.txt | 232 # Android has pthread as part of its c library, not as a separate
|
Completed in 70 milliseconds
