Lines Matching refs:program

97 these event sources and provide your program with events.
203 version of the library your program was compiled against.
350 one calling C<ev_run> or otherwise qualifies as "the main program".
399 If this flag bit is or'ed into the flag value (or the program runs setuid
457 It's also required by POSIX in a threaded program, as libev calls
509 0.1ms) and so on. The biggest issue is fork races, however - if a program
786 A typical use case would be an interactive program such as a game:  When
789 the program was suspended. This can be achieved by calling C<ev_suspend>
822 relying on all watchers to be stopped when deciding when a program has
823 finished (especially in interactive programs), but having a program
837 events while doing lengthy calculations, to keep the program responsive.
960 The idea is that sometimes your program runs just fast enough to handle
962 program responsive, it also wastes a lot of CPU time to poll for new
992 saving power, as the program will "bundle" timer callback invocations that
1232 bug in your program.
1494 timeouts. Under load, data might be received while the program handles
1558 enables your program to keep a lower latency for important connections
1598 with a relatively standard program structure. Thus it is best to always
1600 preferable to a program hanging until some data arrives.
1647 representing files, and expect it to become ready when their program
1690 when writing to a pipe whose other end has been closed, your program gets
1691 sent a SIGPIPE, which, by default, aborts your program. For most programs
1708 typically causing the program to loop at 100% CPU usage.
1716 - when the program encounters an overload, it will just loop until the
1727 If your program is single-threaded, then you could also keep a dummy file
2088 system is suspended. That means, on resume, it will be as if the program
2099 time jump in the monotonic clocks and the realtime clock. If the program
2126 trigger at exactly 10 second intervals. If, however, your program cannot
2338 program when the crontabs have changed).
2903      // now do something you wanted to do when the program has
3326 program, worker threads and so on - you just to make sure to destroy the
3492 the event loop (or your program) is processing events. That means that
3717    // exit main program, after modal loop is finished
4796 your program might be left out as well - a binary starting a timer and an
4817 somewhat, but if your program doesn't otherwise depend on stdio and your
4938 For a real-world example of a program the includes libev
5151 descriptors you can pass in to 1024 - your program suddenly crashes when
5164 without C<-D_REENTRANT> in a threaded program, which, of course, isn't
5174 releases. If you run into high CPU usage, your program freezes or you get
5180 If you can't get it to work, you can try running the program by setting
5224 is not recommended (and not reasonable). If your program needs to use
5320 allowed in a threaded program (C<pthread_sigmask> has to be used). Typical