… | |
… | |
52 | =item scope_guard BLOCK |
52 | =item scope_guard BLOCK |
53 | |
53 | |
54 | Registers a block that is executed when the current scope (block, |
54 | Registers a block that is executed when the current scope (block, |
55 | function, method, eval etc.) is exited. |
55 | function, method, eval etc.) is exited. |
56 | |
56 | |
|
|
57 | See the EXCEPTIONS section for an explanation of how exceptions |
|
|
58 | (i.e. C<die>) are handled inside guard blocks. |
|
|
59 | |
57 | The description below sounds a bit complicated, but that's just because |
60 | The description below sounds a bit complicated, but that's just because |
58 | C<scope_guard> tries to get even corner cases "right": the goal is to |
61 | C<scope_guard> tries to get even corner cases "right": the goal is to |
59 | provide you with a rock solid clean up tool. |
62 | provide you with a rock solid clean up tool. |
60 | |
63 | |
61 | This is similar to this code fragment: |
64 | The behaviour is similar to this code fragment: |
62 | |
65 | |
63 | eval ... code following scope_guard ... |
66 | eval ... code following scope_guard ... |
64 | { |
67 | { |
65 | local $@; |
68 | local $@; |
66 | eval BLOCK; |
69 | eval BLOCK; |
… | |
… | |
70 | |
73 | |
71 | Except it is much faster, and the whole thing gets executed even when the |
74 | Except it is much faster, and the whole thing gets executed even when the |
72 | BLOCK calls C<exit>, C<goto>, C<last> or escapes via other means. |
75 | BLOCK calls C<exit>, C<goto>, C<last> or escapes via other means. |
73 | |
76 | |
74 | If multiple BLOCKs are registered to the same scope, they will be executed |
77 | If multiple BLOCKs are registered to the same scope, they will be executed |
75 | in reverse order. Stuff like C<local> is managed via the same mechanism, |
78 | in reverse order. Other scope-related things such as C<local> are managed |
76 | so variables C<local>ised after calling C<scope_guard> will be restored |
79 | via the same mechanism, so variables C<local>ised I<after> calling |
77 | when the guard runs. |
80 | C<scope_guard> will be restored when the guard runs. |
78 | |
|
|
79 | See B<EXCEPTIONS>, below, for an explanation of exception handling |
|
|
80 | (C<die>) within guard blocks. |
|
|
81 | |
81 | |
82 | Example: temporarily change the timezone for the current process, |
82 | Example: temporarily change the timezone for the current process, |
83 | ensuring it will be reset when the C<if> scope is exited: |
83 | ensuring it will be reset when the C<if> scope is exited: |
84 | |
84 | |
85 | use Guard; |
85 | use Guard; |
… | |
… | |
103 | when the BLOCK gets executed: when the last reference to the object gets |
103 | when the BLOCK gets executed: when the last reference to the object gets |
104 | destroyed, the BLOCK gets executed as with C<scope_guard>. |
104 | destroyed, the BLOCK gets executed as with C<scope_guard>. |
105 | |
105 | |
106 | The returned object can be copied as many times as you want. |
106 | The returned object can be copied as many times as you want. |
107 | |
107 | |
108 | See B<EXCEPTIONS>, below, for an explanation of exception handling |
108 | See the EXCEPTIONS section for an explanation of how exceptions |
109 | (C<die>) within guard blocks. |
109 | (i.e. C<die>) are handled inside guard blocks. |
110 | |
110 | |
111 | Example: acquire a Coro::Semaphore for a second by registering a |
111 | Example: acquire a Coro::Semaphore for a second by registering a |
112 | timer. The timer callback references the guard used to unlock it again. |
112 | timer. The timer callback references the guard used to unlock it again. |
113 | |
113 | |
114 | use AnyEvent; |
114 | use AnyEvent; |