| … | |
… | |
| 133 | |
133 | |
| 134 | The advantage of doing this with a guard instead of simply calling C<< |
134 | The advantage of doing this with a guard instead of simply calling C<< |
| 135 | $sem->down >> in the callback is that you can opt not to create the timer, |
135 | $sem->down >> in the callback is that you can opt not to create the timer, |
| 136 | or your code can throw an exception before it can create the timer, or you |
136 | or your code can throw an exception before it can create the timer, or you |
| 137 | can create multiple timers or other event watchers and only when the last |
137 | can create multiple timers or other event watchers and only when the last |
| 138 | one gets executed will the lock be unlocked. |
138 | one gets executed will the lock be unlocked. Using the C<guard>, you do |
|
|
139 | not have to worry about catching all the places where you have to unlock |
|
|
140 | the semaphore. |
| 139 | |
141 | |
| 140 | =item Guard::cancel $guard |
142 | =item Guard::cancel $guard |
| 141 | |
143 | |
| 142 | Calling this function will "disable" the guard object returned by the |
144 | Calling this function will "disable" the guard object returned by the |
| 143 | C<guard> function, i.e. it will free the BLOCK originally passed to |
145 | C<guard> function, i.e. it will free the BLOCK originally passed to |
