ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.pod
(Generate patch)

Comparing libev/ev.pod (file contents):
Revision 1.458 by root, Fri Dec 20 20:51:46 2019 UTC vs.
Revision 1.460 by root, Wed Jan 22 02:00:13 2020 UTC

… …
1218with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher 1218with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher
1219*) >>), and you can stop watching for events at any time by calling the 1219*) >>), and you can stop watching for events at any time by calling the
1220corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. 1220corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>.
1221 1221
1222As long as your watcher is active (has been started but not stopped) you 1222As long as your watcher is active (has been started but not stopped) you
1223must not touch the values stored in it. Most specifically you must never 1223must not touch the values stored in it except when explicitly documented
1224reinitialise it or call its C<ev_TYPE_set> macro. 1224otherwise. Most specifically you must never reinitialise it or call its
1225C<ev_TYPE_set> macro.
1225 1226
1226Each and every callback receives the event loop pointer as first, the 1227Each and every callback receives the event loop pointer as first, the
1227registered watcher structure as second, and a bitset of received events as 1228registered watcher structure as second, and a bitset of received events as
1228third argument. 1229third argument.
1229 1230
… …
1648 1649
1649This section describes each watcher in detail, but will not repeat 1650This section describes each watcher in detail, but will not repeat
1650information given in the last section. Any initialisation/set macros, 1651information given in the last section. Any initialisation/set macros,
1651functions and members specific to the watcher type are explained. 1652functions and members specific to the watcher type are explained.
1652 1653
1653Members are additionally marked with either I<[read-only]>, meaning that, 1654Most members are additionally marked with either I<[read-only]>, meaning
1654while the watcher is active, you can look at the member and expect some 1655that, while the watcher is active, you can look at the member and expect
1655sensible content, but you must not modify it (you can modify it while the 1656some sensible content, but you must not modify it (you can modify it while
1656watcher is stopped to your hearts content), or I<[read-write]>, which 1657the watcher is stopped to your hearts content), or I<[read-write]>, which
1657means you can expect it to have some sensible content while the watcher 1658means you can expect it to have some sensible content while the watcher
1658is active, but you can also modify it. Modifying it may not do something 1659is active, but you can also modify it. Modifying it may not do something
1659sensible or take immediate effect (or do anything at all), but libev will 1660sensible or take immediate effect (or do anything at all), but libev will
1660not crash or malfunction in any way. 1661not crash or malfunction in any way.
1661 1662
1663In any case, the documentation for each member will explain what the
1664effects are, and if there are any additional access restrictions.
1662 1665
1663=head2 C<ev_io> - is this file descriptor readable or writable? 1666=head2 C<ev_io> - is this file descriptor readable or writable?
1664 1667
1665I/O watchers check whether a file descriptor is readable or writable 1668I/O watchers check whether a file descriptor is readable or writable
1666in each iteration of the event loop, or, more precisely, when reading 1669in each iteration of the event loop, or, more precisely, when reading
… …
1829 1832
1830Configures an C<ev_io> watcher. The C<fd> is the file descriptor to 1833Configures an C<ev_io> watcher. The C<fd> is the file descriptor to
1831receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or 1834receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or
1832C<EV_READ | EV_WRITE>, to express the desire to receive the given events. 1835C<EV_READ | EV_WRITE>, to express the desire to receive the given events.
1833 1836
1834=item int fd [read-only] 1837=item ev_io_modify (ev_io *, int events)
1835 1838
1836The file descriptor being watched. 1839Similar to C<ev_io_set>, but only changes the event mask. Using this might
1840be faster with some backends, as libev can assume that the C<fd> still
1841refers to the same underlying file description, something it cannot do
1842when using C<ev_io_set>.
1837 1843
1844=item int fd [no-modify]
1845
1846The file descriptor being watched. While it can be read at any time, you
1847must not modify this member even when the watcher is stopped - always use
1848C<ev_io_set> for that.
1849
1838=item int events [read-only] 1850=item int events [no-modify]
1839 1851
1840The events being watched. 1852The set of events the fd is being watched for, among other flags. Remember
1853that this is a bit set - to test for C<EV_READ>, use C<< w->events &
1854EV_READ >>, and similarly for C<EV_WRITE>.
1855
1856As with C<fd>, you must not modify this member even when the watcher is
1857stopped, always use C<ev_io_set> or C<ev_io_modify> for that.
1841 1858
1842=back 1859=back
1843 1860
1844=head3 Examples 1861=head3 Examples
1845 1862

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines