summaryrefslogtreecommitdiff
path: root/eio.pod
diff options
context:
space:
mode:
authorroot <root>2011-09-26 16:54:25 +0000
committerroot <root>2011-09-26 16:54:25 +0000
commit85e20119f3aa5693101350fe5674d3e7d8b39f92 (patch)
tree6dc20b89839ee987824236c00bbe45f15e7cac38 /eio.pod
parenta32e991129f96e98d1522356d3a2e51eae0194f6 (diff)
preliminary wd support
Diffstat (limited to 'eio.pod')
-rw-r--r--eio.pod8
1 files changed, 6 insertions, 2 deletions
diff --git a/eio.pod b/eio.pod
index da5f33c..34918b6 100644
--- a/eio.pod
+++ b/eio.pod
@@ -235,13 +235,17 @@ The C<void *data> member simply stores the value of the C<data> argument.
=back
+Memmbers not explicitly described as accessible must not be
+accessed. Specifically, there is no gurantee that any members will still
+have the value they had when the request was submitted.
+
The return value of the callback is normally C<0>, which tells libeio to
continue normally. If a callback returns a nonzero value, libeio will
stop processing results (in C<eio_poll>) and will return the value to its
caller.
-Memory areas passed to libeio must stay valid as long as a request
-executes, with the exception of paths, which are being copied
+Memory areas passed to libeio wrappers must stay valid as long as a
+request executes, with the exception of paths, which are being copied
internally. Any memory libeio itself allocates will be freed after the
finish callback has been called. If you want to manage all memory passed
to libeio yourself you can use the low-level API.