I suggest you to add information about "FUNCTIONS CONTROLLING EVENT LOOPS" to several libev document sections.

[裕士辻]

Dear All.

I have two suggestions to update document, for understanding good points of
libev more.

1. Add *'See also the "FUNCTIONS CONTROLLING EVENT LOOPS" for more detail
of functions.'* at the end of "EXAMPLE PROGRAM".
2. Add *'(It can use by "ev_set_userdata" and "ev_userdata")'* after *'Each
watcher has, by default, a void *data member that ... ignore it.'* at
"ASSOCIATING CUSTOM DATA WITH A WATCHER".

Both of them are for arguing "FUNCTIONS CONTROLLING EVENT LOOPS" more , and
for  finding "userdata" area easier.

## Reason why:

About two weeks ago, I asked you to "stop API of ev_once event?".
Because I couldn't find userdata yet at that time. I only found ev_once to
set user data in libev.
It was difficult for me to find "userdata" area in WATCHER.

I searched information by following steps:
1. See "WHAT TO READ WHEN IN A HURRY" and check "ANATOMY OF A WATCHER",
"EXAMPLE PROGRAM" (almost "EXAMPLE PROGRAM" ).
2. From example, I wonder "how to set user data in callback?" and search it.
3. I find ev_once first. (I don't know why I searched a keyword "user" :-()
4. I assume that "user data is used only ev_once".
=> So I misunderstood the ev_once to use user data, and wanted to stop API.

After that, I could find it by your suggestion and some information.
And I thought 'Oh, I'm too fool, why didn't I read "FUNCTIONS CONTROLLING
EVENT LOOPS"'.

Now I think it has one of the most important part of the libev document.
So I think why don't libev document argues "FUNCTIONS CONTROLLING EVENT
LOOPS" more (especially userdata information).

That is why I suggest two things.


Thank you for your support, I can implement faster event watcher by libev.
I want more than developer use it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schmorp.de/pipermail/libev/attachments/20180730/7143c1f1/attachment.html>