… | |
… | |
2 | |
2 | |
3 | Guard - safe cleanup blocks |
3 | Guard - safe cleanup blocks |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use Guard; |
7 | use Guard; |
8 | |
8 | |
9 | # temporarily chdir to "/etc" directory, but make sure |
9 | # temporarily chdir to "/etc" directory, but make sure |
10 | # to go back to "/" no matter how myfun exits: |
10 | # to go back to "/" no matter how myfun exits: |
11 | sub dosomething { |
11 | sub myfun { |
12 | scope_guard { chdir "/" }; |
12 | scope_guard { chdir "/" }; |
13 | chdir "/etc"; |
13 | chdir "/etc"; |
14 | |
14 | |
15 | call_function_that_might_die_or_other_fun_stuff; |
15 | code_that_might_die_or_does_other_fun_stuff; |
16 | } |
16 | } |
|
|
17 | |
|
|
18 | # create an object that, when the last reference to it is gone, |
|
|
19 | # invokes the given codeblock: |
|
|
20 | my $guard = guard { print "destroyed!\n" }; |
|
|
21 | undef $guard; # probably destroyed here |
17 | |
22 | |
18 | =head1 DESCRIPTION |
23 | =head1 DESCRIPTION |
19 | |
24 | |
20 | This module implements so-called "guards". A guard is something (usually |
25 | This module implements so-called "guards". A guard is something (usually |
21 | an object) that "guards" a resource, ensuring that it is cleaned up when |
26 | an object) that "guards" a resource, ensuring that it is cleaned up when |
… | |
… | |
34 | |
39 | |
35 | =cut |
40 | =cut |
36 | |
41 | |
37 | package Guard; |
42 | package Guard; |
38 | |
43 | |
|
|
44 | no warnings; |
|
|
45 | |
39 | BEGIN { |
46 | BEGIN { |
40 | $VERSION = '0.1'; |
47 | $VERSION = '1.02'; |
41 | @ISA = qw(Exporter); |
48 | @ISA = qw(Exporter); |
42 | @EXPORT = qw(guard scope_guard); |
49 | @EXPORT = qw(guard scope_guard); |
43 | |
50 | |
44 | require Exporter; |
51 | require Exporter; |
45 | |
52 | |
… | |
… | |
52 | =item scope_guard BLOCK |
59 | =item scope_guard BLOCK |
53 | |
60 | |
54 | Registers a block that is executed when the current scope (block, |
61 | Registers a block that is executed when the current scope (block, |
55 | function, method, eval etc.) is exited. |
62 | function, method, eval etc.) is exited. |
56 | |
63 | |
|
|
64 | See the EXCEPTIONS section for an explanation of how exceptions |
|
|
65 | (i.e. C<die>) are handled inside guard blocks. |
|
|
66 | |
57 | The description below sounds a bit complicated, but that's just because |
67 | 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 |
68 | C<scope_guard> tries to get even corner cases "right": the goal is to |
59 | provide you with a rock solid clean up tool. |
69 | provide you with a rock solid clean up tool. |
60 | |
70 | |
61 | This is similar to this code fragment: |
71 | The behaviour is similar to this code fragment: |
62 | |
72 | |
63 | eval ... code following scope_guard ... |
73 | eval ... code following scope_guard ... |
64 | { |
74 | { |
65 | local $@; |
75 | local $@; |
66 | eval BLOCK; |
76 | eval BLOCK; |
… | |
… | |
70 | |
80 | |
71 | Except it is much faster, and the whole thing gets executed even when the |
81 | 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. |
82 | BLOCK calls C<exit>, C<goto>, C<last> or escapes via other means. |
73 | |
83 | |
74 | If multiple BLOCKs are registered to the same scope, they will be executed |
84 | 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, |
85 | 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 |
86 | via the same mechanism, so variables C<local>ised I<after> calling |
77 | when the guard runs. |
87 | 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 | |
88 | |
82 | Example: temporarily change the timezone for the current process, |
89 | Example: temporarily change the timezone for the current process, |
83 | ensuring it will be reset when the C<if> scope is exited: |
90 | ensuring it will be reset when the C<if> scope is exited: |
84 | |
91 | |
85 | use Guard; |
92 | use Guard; |
… | |
… | |
103 | when the BLOCK gets executed: when the last reference to the object gets |
110 | when the BLOCK gets executed: when the last reference to the object gets |
104 | destroyed, the BLOCK gets executed as with C<scope_guard>. |
111 | destroyed, the BLOCK gets executed as with C<scope_guard>. |
105 | |
112 | |
106 | The returned object can be copied as many times as you want. |
113 | The returned object can be copied as many times as you want. |
107 | |
114 | |
108 | See B<EXCEPTIONS>, below, for an explanation of exception handling |
115 | See the EXCEPTIONS section for an explanation of how exceptions |
109 | (C<die>) within guard blocks. |
116 | (i.e. C<die>) are handled inside guard blocks. |
110 | |
117 | |
111 | Example: acquire a Coro::Semaphore for a second by registering a |
118 | Example: acquire a Coro::Semaphore for a second by registering a |
112 | timer. The timer callback references the guard used to unlock it again. |
119 | timer. The timer callback references the guard used to unlock it |
|
|
120 | again. (Please ignore the fact that C<Coro::Semaphore> has a C<guard> |
|
|
121 | method that does this already): |
113 | |
122 | |
|
|
123 | use Guard; |
114 | use AnyEvent; |
124 | use AnyEvent; |
115 | use Coro::Semaphore; |
125 | use Coro::Semaphore; |
116 | |
126 | |
117 | my $sem = new Coro::Semaphore; |
127 | my $sem = new Coro::Semaphore; |
118 | |
128 | |
119 | sub lock_1s { |
129 | sub lock_for_a_second { |
120 | $sem->down; |
130 | $sem->down; |
121 | my $guard = guard { $sem->up }; |
131 | my $guard = guard { $sem->up }; |
122 | |
132 | |
123 | my $timer; |
133 | my $timer; |
124 | $timer = AnyEvent->timer (after => 1, sub { |
134 | $timer = AnyEvent->timer (after => 1, sub { |
… | |
… | |
130 | |
140 | |
131 | The advantage of doing this with a guard instead of simply calling C<< |
141 | The advantage of doing this with a guard instead of simply calling C<< |
132 | $sem->down >> in the callback is that you can opt not to create the timer, |
142 | $sem->down >> in the callback is that you can opt not to create the timer, |
133 | or your code can throw an exception before it can create the timer, or you |
143 | or your code can throw an exception before it can create the timer, or you |
134 | can create multiple timers or other event watchers and only when the last |
144 | can create multiple timers or other event watchers and only when the last |
135 | one gets executed will the lock be unlocked. |
145 | one gets executed will the lock be unlocked. Using the C<guard>, you do |
|
|
146 | not have to worry about catching all the places where you have to unlock |
|
|
147 | the semaphore. |
136 | |
148 | |
137 | =item Guard::cancel $guard |
149 | =item $guard->cancel |
138 | |
150 | |
139 | Calling this function will "disable" the guard object returned by the |
151 | Calling this function will "disable" the guard object returned by the |
140 | C<guard> function, i.e. it will free the BLOCK originally passed to |
152 | C<guard> function, i.e. it will free the BLOCK originally passed to |
141 | C<guard >and will arrange for the BLOCK not to be executed. |
153 | C<guard >and will arrange for the BLOCK not to be executed. |
142 | |
154 | |
… | |
… | |
155 | all, they are usually used to clean up after such exceptions. However, if |
167 | all, they are usually used to clean up after such exceptions. However, if |
156 | something truly exceptional is happening, a guard block should be allowed |
168 | something truly exceptional is happening, a guard block should be allowed |
157 | to die. Also, programming errors are a large source of exceptions, and the |
169 | to die. Also, programming errors are a large source of exceptions, and the |
158 | programmer certainly wants to know about those. |
170 | programmer certainly wants to know about those. |
159 | |
171 | |
160 | Since in most cases, the block executing when the guard gets executes does |
172 | Since in most cases, the block executing when the guard gets executed does |
161 | not know or does not care about the guard blocks, it makes little sense to |
173 | not know or does not care about the guard blocks, it makes little sense to |
162 | let containing code handle the exception. |
174 | let containing code handle the exception. |
163 | |
175 | |
164 | Therefore, whenever a guard block throws an exception, it will be caught, |
176 | Therefore, whenever a guard block throws an exception, it will be caught, |
165 | and this module will call the code reference stored in C<$Guard::DIED> |
177 | followed by calling the code reference stored in C<$Guard::DIED> (with |
166 | (with C<$@> set to the actual exception), which is similar to how most |
178 | C<$@> set to the actual exception), which is similar to how most event |
167 | event loops handle this case. |
179 | loops handle this case. |
|
|
180 | |
|
|
181 | The default for C<$Guard::DIED> is to call C<warn "$@">. |
|
|
182 | |
|
|
183 | The C<$@> variable will be restored to its value before the guard call in |
|
|
184 | all cases, so guards will not disturb C<$@> in any way. |
168 | |
185 | |
169 | The code reference stored in C<$Guard::DIED> should not die (behaviour is |
186 | The code reference stored in C<$Guard::DIED> should not die (behaviour is |
170 | not guaranteed, but right now, the exception will simply be ignored). |
187 | not guaranteed, but right now, the exception will simply be ignored). |
171 | |
188 | |
172 | The default for C<$Guard::DIED> is to call C<warn "$@">. |
|
|
173 | |
|
|
174 | =head1 AUTHOR |
189 | =head1 AUTHOR |
175 | |
190 | |
176 | Marc Lehmann <schmorp@schmorp.de> |
191 | Marc Lehmann <schmorp@schmorp.de> |
177 | http://home.schmorp.de/ |
192 | http://home.schmorp.de/ |
178 | |
193 | |
179 | =head1 THANKS |
194 | =head1 THANKS |
180 | |
195 | |
181 | Thanks to Marco Maisenhelder, who reminded me of the C<$Guard::DIED> |
196 | Thanks to Marco Maisenhelder, who reminded me of the C<$Guard::DIED> |
182 | solution to the problem of exceptions. |
197 | solution to the problem of exceptions. |
183 | |
198 | |
|
|
199 | =head1 SEE ALSO |
|
|
200 | |
|
|
201 | L<Scope::Guard> and L<Sub::ScopeFinalizer>, which actually implement |
|
|
202 | dynamic, not scoped guards, and have a lot higher CPU, memory and typing |
|
|
203 | overhead. |
|
|
204 | |
|
|
205 | L<Hook::Scope>, which has apparently never been finished and corrupts |
|
|
206 | memory when used. |
|
|
207 | |
184 | =cut |
208 | =cut |
185 | |
209 | |