| … | |
… | |
| 1653 | |
1653 | |
| 1654 | Most members are additionally marked with either I<[read-only]>, meaning |
1654 | Most members are additionally marked with either I<[read-only]>, meaning |
| 1655 | that, while the watcher is active, you can look at the member and expect |
1655 | that, while the watcher is active, you can look at the member and expect |
| 1656 | some sensible content, but you must not modify it (you can modify it while |
1656 | some sensible content, but you must not modify it (you can modify it while |
| 1657 | the watcher is stopped to your hearts content), or I<[read-write]>, which |
1657 | the watcher is stopped to your hearts content), or I<[read-write]>, which |
| 1658 | means you can expect it to have some sensible content while the watcher |
1658 | means you can expect it to have some sensible content while the watcher is |
| 1659 | is active, but you can also modify it. Modifying it may not do something |
1659 | active, but you can also modify it (within the same thread as the event |
|
|
1660 | loop, i.e. without creating data races). Modifying it may not do something |
| 1660 | sensible or take immediate effect (or do anything at all), but libev will |
1661 | sensible or take immediate effect (or do anything at all), but libev will |
| 1661 | not crash or malfunction in any way. |
1662 | not crash or malfunction in any way. |
| 1662 | |
1663 | |
| 1663 | In any case, the documentation for each member will explain what the |
1664 | In any case, the documentation for each member will explain what the |
| 1664 | effects are, and if there are any additional access restrictions. |
1665 | effects are, and if there are any additional access restrictions. |
