fix documentation to follow what actually happens

This commit is contained in:
Lennart Poettering 2008-08-04 23:33:10 +02:00
parent 64a23677d3
commit 163f10712e

View file

@ -52,14 +52,14 @@
* Some objects can have multiple entries at the server. When requesting all * Some objects can have multiple entries at the server. When requesting all
* of these at once, the callback will be called multiple times, once for * of these at once, the callback will be called multiple times, once for
* each object. When the list has been exhausted, the callback will be called * each object. When the list has been exhausted, the callback will be called
* without an information structure and the eol parameter set to a non-zero * without an information structure and the eol parameter set to a positive
* value. * value.
* *
* Note that even if a single object is requested, and not the entire list, * Note that even if a single object is requested, and not the entire list,
* the terminating call will still be made. * the terminating call will still be made.
* *
* If an error occurs, the callback will be called without and information * If an error occurs, the callback will be called without and information
* structure and eol set to zero. * structure and eol set to a negative value..
* *
* Data members in the information structures are only valid during the * Data members in the information structures are only valid during the
* duration of the callback. If they are required after the callback is * duration of the callback. If they are required after the callback is