Home
last modified time | relevance | path

Searched refs:in (Results 1 – 25 of 64) sorted by relevance

123

/libuv/docs/
H A Dmake.bat45 for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
68 echo.Build finished. The HTML pages are in %BUILDDIR%/html.
109 .hhp project file in %BUILDDIR%/htmlhelp.
118 .qhcp project file in %BUILDDIR%/qthelp, like this:
137 echo.Build finished. The epub file is in %BUILDDIR%/epub.
155 echo.Build finished; the PDF files are in %BUILDDIR%/latex.
165 echo.Build finished; the PDF files are in %BUILDDIR%/latex.
205 echo.The overview file is in %BUILDDIR%/changes.
214 or in %BUILDDIR%/linkcheck/output.txt.
223 results in %BUILDDIR%/doctest/output.txt.
[all …]
/libuv/docs/src/
H A Dloop.rst85 spends in the event provider.
125 zero in all other cases.
129 you should run the event loop again sometime in the future).
133 you should run the event loop again sometime in the future).
140 requests or closing handles in the loop.
160 poll in one thread and run the event loop's callbacks in another see
206 Previously started watchers will continue to be started in the
210 loop created in the parent process that you plan to continue to
211 use in the child, including the default loop (even if you don't
214 the loop in the child. Failure to do so will result in undefined
[all …]
H A Dmisc.rst24 Total bytes in the buffer.
475 interface identifier in scoped IPv6 addresses, e.g.
523 On Unix the path no longer ends in a slash.
619 the kernel (in bytes). Returns 0 when unknown.
623 Gets the total amount of physical memory in the system (in bytes).
663 be in nanoseconds.
671 to time adjustments; it can jump back in time.
674 jumps back in time.
901 Convert UTF-16 (or UCS-2) data in `utf16` to WTF-8 data in `*wtf8_ptr`. The
907 returned in `wtf8_ptr` and the length will be returned in `wtf8_len_ptr`.
[all …]
H A Dmetrics.rst17 these metrics in a :c:type:`uv_prepare_cb` in order to make sure there are
53 Retrieve the amount of time the event loop has been idle in the kernel's
56 The return value is the accumulated time spent idle in the kernel's event
H A Dmigration_010_100.rst46 Error handling had a major overhaul in libuv 1.0. In general, functions and status parameters
51 a negative number in case of error.
191 data on a pipe, which could also result in the reception of handles over it. The callback
204 handles using :c:func:`uv_pipe_pending_count` and :c:func:`uv_pipe_pending_type` while in
224 While it wasn't supported by the API, users often accessed the libuv internals in
237 `uv_fs_readdir` returned a list of strings in the `req->ptr` field upon completion in
H A Dstream.rst9 in the form of :c:type:`uv_tcp_t`, :c:type:`uv_pipe_t` and :c:type:`uv_tty_t`.
30 this type. When a stream is in non-blocking mode, write requests sent
41 the `buf` parameter might not point to a valid buffer; in that case
58 Callback called after data was written on a stream. `status` will be 0 in
64 `status` will be 0 in case of success, < 0 otherwise.
69 be 0 in case of success, < 0 otherwise.
75 `status` will be 0 in case of success, < 0 otherwise.
123 This call is used in conjunction with :c:func:`uv_listen` to accept incoming
161 Write data to stream. Buffers are written in order. Example:
240 significantly in the future.
/libuv/src/
H A Dthread-common.c57 b->in = 0; in uv_barrier_init()
104 if (++b->in == b->threshold) { in uv_barrier_wait()
105 b->in = 0; in uv_barrier_wait()
111 while (b->in != 0); in uv_barrier_wait()
134 assert(b->in == 0); in uv_barrier_destroy()
138 if (b->in != 0) in uv_barrier_destroy()
/libuv/m4/
H A Dax_pthread.m426 # variables in your default LIBS, CFLAGS, and CC:
97 # It gets checked for in the link test anyway.
137 # none: in case threads are in libc; should be tried before -Kthread and
153 case $host_os in
210 case $host_os in
248 # option in a rather... idiosyncratic way
280 # flag that is used only in the compilation phase and not in
324 for ax_pthread_try_flag in $ax_pthread_flags; do
326 case $ax_pthread_try_flag in
427 case $host_os in
[all …]
H A Das_case.m44 # | case WORD in
18 [case $1 in
/libuv/
H A DChangeLog9 * win: Fix linked list logic in getaddrinfo (Thad House)
39 * win,fs: fix bug in fs__readdir (Hüseyin Açacak)
89 * doc: fix typos in ChangeLog (tgolang)
713 * win: fix leak in uv_chdir (Trevor Norris)
2091 * doc: fix typo in basics.rst (Nan Xiao)
4028 * doc: fix typo in README (Angel Leon)
4310 * doc: fix typo in tcp.rst (Igor Soarez)
4467 * test: use modified path in test (cjihrig)
4915 * build: use same CFLAGS in autotools build as in gyp (Saúl Ibarra Corretgé)
5555 * include: fix typo in comment in uv.h (Ben Noordhuis)
[all …]
H A DLICENSE-docs20 and certain other rights specified in the public license below. The
26 permission to use material in ways otherwise restricted by
48 rights in the material. A licensor may make special requests,
73 and in which the Licensed Material is translated, altered,
79 synched in timed relation with a moving image.
82 and Similar Rights in Your contributions to Adapted Material in
127 equivalent rights anywhere in the world.
143 in part; and
187 provided in Section 3(a)(1)(A)(i).
246 2. You may satisfy the conditions in Section 3(a)(1) in any
[all …]
H A DSECURITY.md5 Currently, we are providing security updates for the latest release in the v1.x series:
13 …in `libuv`, please use the [GitHub's private vulnerability reporting feature](https://docs.github.…
24 * Post any information about the vulnerability in public places.
H A DSUPPORTED_PLATFORMS.md38 will need to implement some of the functions, the prototypes are in
42 new include file in ``include/`` with the name ``uv-theplatform.h`` and add
45 All functionality related to the new platform must be implemented in its own
46 file inside ``src/unix/`` unless it's already done in a common file, in which
59 new API is to be used, it must be done optionally, only in supported versions.
H A DREADME.md62 framework, which makes it possible to build the documentation in multiple
122 is necessary. Key IDs are listed in the
146 Starting with libuv 1.7.0, the tarballs stored in the
175 and tools which can be included in the global `PATH`.
222 Make sure that you specify the architecture you wish to build for in the
258 The list of all tests is in `test/test-list.h`.
267 This invocation will cause the test driver to execute the test in
306 listed in `test/benchmark-list.h`.
314 It is recommended to turn on the `-fno-strict-aliasing` compiler flag in
316 may not be safe in the presence of compiler optimizations that depend on
[all …]
H A DCONTRIBUTING.md25 In case of doubt, open an issue in the [issue tracker][], post your question
50 * Code that is specific to unix-y platforms should be placed in `src/unix`, and
55 be declared in `include/uv/win.h`.
60 prefixed with `uv_` (or `UV_` in case of macros).
108 subsystem: explaining the commit in one line
111 in more detail, possibly giving some background about the issue
139 Bug fixes and features should come with tests. Add your tests in the
140 `test/` directory. Each new test needs to be registered in `test/test-list.h`.
142 If you add a new test file, it needs to be registered in three places:
162 to address, apply your changes in a separate commit and push that to your
[all …]
H A DLICENSE-extra9 deal in the Software without restriction, including without limitation the
14 The above copyright notice and this permission notice shall be included in
34 - inet_pton and inet_ntop implementations, contained in src/inet.c, are
/libuv/test/fixtures/
H A Dlorem_ipsum.txt1 …e dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur…
/libuv/docs/src/guide/
H A Dbasics.rst12 In event-driven programming, an application expresses interest in certain events
44 started in a separate thread (or in a thread pool). When the blocking function
52 operating system to watch the socket and put an event notification in the
56 point, then used the data at another point (in time and space). It is
58 This fits in well with libuv's event-loop approach, since the operating system
60 that other events can continue to be handled as fast as they come in [#]_.
64 How the I/O is run in the background is not of our concern, but due to the
67 polling to perform tasks in a non-blocking manner.
73 libuv's event loop is explained in more detail in the `documentation
139 libuv works by the user expressing interest in particular events. This is
[all …]
H A Dthreads.rst5 way** to do *web-scale programming*? Well... no. Threads are still the medium in
21 required, signal errors directly via return values, and, as shown in the
29 running in one thread (the main thread)**. No other thread interacts
72 catalogue any surprises in the libuv APIs here. For the rest you can look at
112 return an error in the second call to ``uv_mutex_lock()``.
124 holding it. Read-write locks are frequently used in databases. Here is a toy
192 a task in a separate thread, and have a callback that is triggered when the
204 own system of running the task in a separate thread. libuv just provides
208 calculate fibonacci numbers, sleeping a bit along the way, but run it in
233 The thread function will be launched in a separate thread, passed the
[all …]
H A Dintroduction.rst13 This book is still a work in progress, so sections may be incomplete, but
26 written in C or C++ with a set of (a)synchronous APIs that are exposed to
27 JavaScript. You will use libuv purely in the context of node.js. For
36 The node.js_ project began in 2009 as a JavaScript environment decoupled
40 node.js grew in popularity, it was important to make it work on Windows, but
63 There is no need to ``make install``. To build the examples run ``make`` in the
H A Dnetworking.rst4 Networking in libuv is not much different from directly using the BSD socket
14 The code samples in this chapter exist to show certain libuv APIs. They are
60 In this case we also establish interest in reading from this stream.
70 be found in the code. Just remember to call ``uv_close`` when the socket isn't
71 required. This can be done even in the ``uv_listen`` callback if you are not
72 interested in accepting the connection.
180 The concepts of multicasting are nicely explained in `this guide`_.
209 callback can be ``NULL`` in which case the function will run synchronously.
213 call ``uv_freeaddrinfo`` in the callback.
254 .. [#] libuv use the system ``getaddrinfo`` in the libuv threadpool. libuv
[all …]
H A Dutilities.rst57 An actual timer example is in the :ref:`reference count section
84 This is also used in node.js where some libuv methods are being bubbled up to
106 CPU time to perform SETI calculations :) An idle watcher is also useful in
121 events we are interested in. ``crunch_away`` will now be called repeatedly
141 This allows cleaning up the work request and all the data in one free call.
202 use these in the event loop thread, use the :ref:`threadpool` instead. Of
289 point libcurl does all of its internal tasks in small increments, and will
327 things in your application [#]_. A sample plugin using this API is:
362 ``uv_dlsym`` stores a pointer to the symbol in the second argument in the third
364 function we are looking for in the application's plugins.
[all …]
H A Deventloops.rst15 that are ready to be processed in this iteration of the loop will still be
29 within the event loop, which is why invoking ``uv_stop()`` in them will still
32 callbacks. If you were to call ``uv_stop()`` in any of them, ``stop_flag``
35 ``uv_stop()`` in one of the check handlers, I/O has already finished and is not
H A Dprocesses.rst8 A common idiom in Unix is for every process to do one thing and do it well. In
10 (similar to using pipes in shells). A multi-process model with messages
15 advantage of multiple cores in modern computers. In a multi-threaded program
71 using fields in ``uv_process_options_t``.
99 * ``UV_PROCESS_DETACHED`` - Starts the child process in a new session, which
219 to ``UV_INHERIT_STREAM`` and setting ``data.stream`` to the stream in the
291 Since domain sockets [#]_ can have a well known name and a location in the
368 Although ``accept`` seems odd in this code, it actually makes sense. What
401 It is in ``on_new_connection`` (the TCP infrastructure is initialized in
403 worker in the round-robin.
[all …]
/libuv/test/
H A Dtest-stdio-over-pipes.c37 static uv_pipe_t in; variable
58 uv_close((uv_handle_t*)&in, close_cb); in exit_cb()
110 r = uv_write(req, (uv_stream_t*) &in, &wrbuf, 1, after_write); in on_read()
129 uv_pipe_init(loop, &in, 0); in test_stdio_over_pipes()
134 options.stdio[0].data.stream = (uv_stream_t*) &in; in test_stdio_over_pipes()

Completed in 50 milliseconds

123