Lines Matching refs:t

140 somewhere near the beginning of 1970, details are complicated, don't
213 Example: Make sure we haven't accidentally been linked against the wrong
297 requested operation, or, if the condition doesn't go away, do bad stuff
352 If you don't know what event loop to use, use the one returned from this
363 C<ev_loop_new> which doesn't do that, or you can simply overwrite the
445 example) that can't properly initialise their signal masks.
467 using this backend. It doesn't scale too well (O(highest_fd)), but its
515 but of course I<doesn't>, and epoll just loves to report events for
541 starting a watcher (without re-setting it) also usually doesn't cause
559 was broken on all BSDs except NetBSD (usually it doesn't work reliably
582 While nominally embeddable in other event loops, this doesn't work
630 Try all backends (even potentially broken ones that wouldn't be tried
704 you just fork+exec or create a new loop in the child, you don't have to
750 throwing an exception etc.), doesn't count as "exit" - consider this
928 before stop> (but only if the watcher wasn't active before, or was active
984 usually doesn't make much sense to set it to a lower value than C<0.01>,
986 you do transactions with the outside world and you can't increase the
989 then you can't do more than 100 transactions per second).
1373 watcher isn't pending it does nothing and returns C<0>.
1586 the watcher if you don't want to act on the event and neither want to
1590 fd as you want (as long as you don't confuse yourself). Setting all file
1607 use C<SIGALRM> and an interval timer, just to be sure you won't block
1648 doesn't block on disk accesses (which can take a long time on their own).
1659 will not send data on its own, simply because it doesn't know what you
1698 =head3 The special problem of accept()ing when you can't
1980 better, and isn't very complicated either. In most case, choosing either
2005 resolution (think windows if you can't come up with a broken enough OS
2073 connection after 100 seconds") then this shouldn't bother you as it is
2272 This doesn't mean there will always be 3600 seconds in between triggers,
2426 handlers as long as you don't register any with libev for the same signal.
2460 So I can't stress this enough: I<If you do not reset your signal mask when
2516 as the event loop isn't entered (or is continued from a watcher), i.e.,
2694 Libev doesn't normally do any kind of I/O itself, and so is not blocking
2698 For local paths, this usually doesn't matter: unless the system is very
2867 For this to work, the idle watcher doesn't need to be invoked at all - the
2954 any other watchers after the poll (this doesn't matter for C<ev_prepare>
2975 next event loop iteration. However, that isn't as soon as possible -
3031      /* the callback is illegal, but won't be called as we stop during check */
3130 =head2 C<ev_embed> - when one backend isn't enough...
3158 sweep and invoke their callbacks (the callback doesn't need to invoke the
3382 multiple-writer-single-reader queue that works in all cases and doesn't
3428 instead of C<sigprocmask> when you use threads, but libev doesn't do it
3574 section only contains stuff that wouldn't fit anywhere else.
3581 don't want to allocate memory separately and store a pointer to it in that
3668 canceling it, which probably isn't working so well when the callback has
3866 doesn't need callbacks anymore.
3883 C<wait_for_event>. (the watcher needs to be started, as always, but it doesn't
4311 will be initialised if it isn't already initialised.
4485 when the functionality isn't available is safe, though, although you have
4534 structure. This is useful if libev doesn't compile due to a missing
4544 select/socket/connect etc. don't understand file descriptors but
4658 If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
4811 doesn't support the required declaration syntax.
4817 somewhat, but if your program doesn't otherwise depend on stdio and your
5000 themselves and don't care/know about threading.
5034 the loop, as long as you don't confuse yourself). The only exception is
5057 wrong (because they don't actually warn about the condition their message
5083 is not a memleak - the memory is still being referenced, and didn't leak.
5090 Keep in mind that valgrind is a very good tool, but only a tool. Don't
5095 is a bug in libev (best check the archives, too :). However, don't be
5110 That means that libev compiled in the default environment doesn't support
5163 thread-unsafe that you can't even use components/libraries compiled
5164 without C<-D_REENTRANT> in a threaded program, which, of course, isn't
5176 and latest kernel patches applied. No, I don't know which ones, but there
5180 If you can't get it to work, you can try running the program by setting
5188 compiled in), which normally isn't a big problem as C<select> works fine
5195 Win32 doesn't support any of the standards (e.g. POSIX) that libev
5215 Not a libev limitation but worth mentioning: windows apparently doesn't
5247 The winsocket C<select> function doesn't follow POSIX in that it
5390 correct watcher to remove. The lists are usually short (you don't usually
5471 Most functions working on C<struct ev_loop> objects don't have an