diff options
author | sf-exg <sf-exg> | 2012-05-07 07:00:00 +0000 |
---|---|---|
committer | sf-exg <sf-exg> | 2012-05-07 07:00:00 +0000 |
commit | e4734317d1681eac71ef631844211645f880ffa3 (patch) | |
tree | edfecce5ad19b73bd6ebc009f13424f999076aa7 | |
parent | 85ba31039c775700f54612dcbfcfc3e7349bab9e (diff) |
Fix typos.
-rw-r--r-- | ev.pod | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -3952,7 +3952,7 @@ will work fine. Proper exception specifications might have to be added to callbacks passed to libev: exceptions may be thrown only from watcher callbacks, all -other callbacks (allocator, syserr, loop acquire/release and periodioc +other callbacks (allocator, syserr, loop acquire/release and periodic reschedule callbacks) must not throw exceptions, and might need a C<throw ()> specification. If you have code that needs to be compiled as both C and C++ you can use the C<EV_THROW> macro for this: @@ -4561,7 +4561,7 @@ the underlying OS handle. If defined to be C<1>, libev will use C<WSASocket> to create its internal communication socket, which works better in some environments. Otherwise, the normal C<socket> function will be used, which works better in other -enviornments. +environments. =item EV_USE_POLL |