| … | |
… | |
| 75 | |
75 | |
| 76 | =head2 AIO FUNCTIONS |
76 | =head2 AIO FUNCTIONS |
| 77 | |
77 | |
| 78 | All the C<aio_*> calls are more or less thin wrappers around the syscall |
78 | All the C<aio_*> calls are more or less thin wrappers around the syscall |
| 79 | with the same name (sans C<aio_>). The arguments are similar or identical, |
79 | with the same name (sans C<aio_>). The arguments are similar or identical, |
| 80 | and they all accept an additional C<$callback> argument which must be |
80 | and they all accept an additional (and optional) C<$callback> argument |
| 81 | a code reference. This code reference will get called with the syscall |
81 | which must be a code reference. This code reference will get called with |
| 82 | return code (e.g. most syscalls return C<-1> on error, unlike perl, which |
82 | the syscall return code (e.g. most syscalls return C<-1> on error, unlike |
| 83 | usually delivers "false") as it's sole argument when the given syscall has |
83 | perl, which usually delivers "false") as it's sole argument when the given |
| 84 | been executed asynchronously. |
84 | syscall has been executed asynchronously. |
| 85 | |
85 | |
| 86 | All functions that expect a filehandle will also accept a file descriptor. |
86 | All functions that expect a filehandle will also accept a file descriptor. |
| 87 | |
87 | |
| 88 | The filenames you pass to these routines I<must> be absolute. The reason |
88 | The filenames you pass to these routines I<must> be absolute. The reason |
| 89 | is that at the time the request is being executed, the current working |
89 | is that at the time the request is being executed, the current working |
