Lines Matching refs:files

525 perfectly fine with C<select> (files, many character devices...).
1644 =head3 The special problem of files
1647 representing files, and expect it to become ready when their program
1652 there, and in the case of open files, that's always the case, so you
1658 on its own, but in the case of files, there is no such thing: the disk
1662 Since files are typically not-so-well supported by advanced notification
1664 to files, even though you should not use it. The reason for this is
1666 usually a tty, often a pipe, but also sometimes files or special devices
1672 So avoid file descriptors pointing to files when you know it (e.g. use
3904 files, F<my_ev.h> and F<my_ev.c> that include the respective libev files:
4350 The goal is to enable you to just copy the necessary files into your
4357 Depending on what features you need you need to include one or more sets of files
4370 it, do the same for F<ev.h> in all files wishing to use this API (best
4377 Both header files and implementation files can be compiled with a C++
4381 You need the following files in your source tree, or in a directory
4397 F<ev.c> includes the backend files directly when enabled, so you only need
4410 in the files that want to use the libevent API. This also includes F<ev.h>.
4412 You need the following additional files for this:
4431 define before including (or compiling) any of its files. The default in
4887 members. You have to define it each time you include one of the files,
4914 exported symbols, you can use the provided F<Symbol.*> files which list
4940 (L<http://software.schmorp.de/pkg/EV.html>). It has the libev files in
4942 interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file
5111 files larger than 2GiB or so, which mainly affects C<ev_stat> watchers.
5240 you do I<not> compile the F<ev.c> or any other embedded source files!):