1 |
root |
1.1 |
=head1 NAME |
2 |
|
|
|
3 |
|
|
Guard - safe cleanup blocks |
4 |
|
|
|
5 |
|
|
=head1 SYNOPSIS |
6 |
|
|
|
7 |
root |
1.9 |
use Guard; |
8 |
|
|
|
9 |
|
|
# temporarily chdir to "/etc" directory, but make sure |
10 |
|
|
# to go back to "/" no matter how myfun exits: |
11 |
|
|
sub myfun { |
12 |
|
|
scope_guard { chdir "/" }; |
13 |
|
|
chdir "/etc"; |
14 |
|
|
|
15 |
|
|
call_function_that_might_die_or_other_fun_stuff; |
16 |
|
|
} |
17 |
root |
1.4 |
|
18 |
root |
1.1 |
=head1 DESCRIPTION |
19 |
|
|
|
20 |
|
|
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 |
22 |
|
|
expected. |
23 |
|
|
|
24 |
|
|
Specifically, this module supports two different types of guards: guard |
25 |
|
|
objects, which execute a given code block when destroyed, and scoped |
26 |
|
|
guards, which are tied to the scope exit. |
27 |
|
|
|
28 |
root |
1.2 |
=head1 FUNCTIONS |
29 |
|
|
|
30 |
|
|
This module currently exports the C<scope_guard> and C<guard> functions by |
31 |
|
|
default. |
32 |
|
|
|
33 |
root |
1.1 |
=over 4 |
34 |
|
|
|
35 |
|
|
=cut |
36 |
|
|
|
37 |
|
|
package Guard; |
38 |
|
|
|
39 |
|
|
BEGIN { |
40 |
root |
1.3 |
$VERSION = '0.1'; |
41 |
root |
1.1 |
@ISA = qw(Exporter); |
42 |
root |
1.3 |
@EXPORT = qw(guard scope_guard); |
43 |
root |
1.1 |
|
44 |
|
|
require Exporter; |
45 |
|
|
|
46 |
|
|
require XSLoader; |
47 |
|
|
XSLoader::load Guard, $VERSION; |
48 |
|
|
} |
49 |
|
|
|
50 |
|
|
our $DIED = sub { warn "$@" }; |
51 |
|
|
|
52 |
|
|
=item scope_guard BLOCK |
53 |
|
|
|
54 |
|
|
Registers a block that is executed when the current scope (block, |
55 |
|
|
function, method, eval etc.) is exited. |
56 |
|
|
|
57 |
root |
1.8 |
See the EXCEPTIONS section for an explanation of how exceptions |
58 |
|
|
(i.e. C<die>) are handled inside guard blocks. |
59 |
|
|
|
60 |
root |
1.2 |
The description below sounds a bit complicated, but that's just because |
61 |
|
|
C<scope_guard> tries to get even corner cases "right": the goal is to |
62 |
|
|
provide you with a rock solid clean up tool. |
63 |
|
|
|
64 |
root |
1.8 |
The behaviour is similar to this code fragment: |
65 |
root |
1.1 |
|
66 |
|
|
eval ... code following scope_guard ... |
67 |
|
|
{ |
68 |
|
|
local $@; |
69 |
|
|
eval BLOCK; |
70 |
|
|
eval { $Guard::DIED->() } if $@; |
71 |
|
|
} |
72 |
root |
1.2 |
die if $@; |
73 |
root |
1.1 |
|
74 |
|
|
Except it is much faster, and the whole thing gets executed even when the |
75 |
|
|
BLOCK calls C<exit>, C<goto>, C<last> or escapes via other means. |
76 |
|
|
|
77 |
root |
1.4 |
If multiple BLOCKs are registered to the same scope, they will be executed |
78 |
root |
1.8 |
in reverse order. Other scope-related things such as C<local> are managed |
79 |
|
|
via the same mechanism, so variables C<local>ised I<after> calling |
80 |
|
|
C<scope_guard> will be restored when the guard runs. |
81 |
root |
1.1 |
|
82 |
root |
1.4 |
Example: temporarily change the timezone for the current process, |
83 |
|
|
ensuring it will be reset when the C<if> scope is exited: |
84 |
|
|
|
85 |
|
|
use Guard; |
86 |
|
|
use POSIX (); |
87 |
|
|
|
88 |
|
|
if ($need_to_switch_tz) { |
89 |
|
|
# make sure we call tzset after $ENV{TZ} has been restored |
90 |
|
|
scope_guard { POSIX::tzset }; |
91 |
root |
1.1 |
|
92 |
root |
1.4 |
# localise after the scope_guard, so it gets undone in time |
93 |
|
|
local $ENV{TZ} = "Europe/London"; |
94 |
|
|
POSIX::tzset; |
95 |
root |
1.1 |
|
96 |
root |
1.4 |
# do something with the new timezone |
97 |
root |
1.1 |
} |
98 |
|
|
|
99 |
|
|
=item my $guard = guard BLOCK |
100 |
|
|
|
101 |
|
|
Behaves the same as C<scope_guard>, except that instead of executing |
102 |
|
|
the block on scope exit, it returns an object whose lifetime determines |
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>. |
105 |
|
|
|
106 |
|
|
The returned object can be copied as many times as you want. |
107 |
|
|
|
108 |
root |
1.8 |
See the EXCEPTIONS section for an explanation of how exceptions |
109 |
|
|
(i.e. C<die>) are handled inside guard blocks. |
110 |
root |
1.1 |
|
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. |
113 |
|
|
|
114 |
root |
1.9 |
use Guard; |
115 |
root |
1.1 |
use AnyEvent; |
116 |
|
|
use Coro::Semaphore; |
117 |
|
|
|
118 |
|
|
my $sem = new Coro::Semaphore; |
119 |
|
|
|
120 |
root |
1.9 |
sub lock_for_a_second { |
121 |
root |
1.1 |
$sem->down; |
122 |
|
|
my $guard = guard { $sem->up }; |
123 |
|
|
|
124 |
|
|
my $timer; |
125 |
|
|
$timer = AnyEvent->timer (after => 1, sub { |
126 |
|
|
# do something |
127 |
|
|
undef $sem; |
128 |
|
|
undef $timer; |
129 |
|
|
}); |
130 |
|
|
} |
131 |
|
|
|
132 |
|
|
The advantage of doing this with a guard instead of simply calling C<< |
133 |
|
|
$sem->down >> in the callback is that you can opt not to create the timer, |
134 |
|
|
or your code can throw an exception before it can create the timer, or you |
135 |
|
|
can create multiple timers or other event watchers and only when the last |
136 |
|
|
one gets executed will the lock be unlocked. |
137 |
|
|
|
138 |
|
|
=item Guard::cancel $guard |
139 |
|
|
|
140 |
|
|
Calling this function will "disable" the guard object returned by the |
141 |
|
|
C<guard> function, i.e. it will free the BLOCK originally passed to |
142 |
|
|
C<guard >and will arrange for the BLOCK not to be executed. |
143 |
|
|
|
144 |
|
|
This can be useful when you use C<guard> to create a fatal cleanup handler |
145 |
|
|
and later decide it is no longer needed. |
146 |
|
|
|
147 |
|
|
=cut |
148 |
|
|
|
149 |
|
|
1; |
150 |
|
|
|
151 |
|
|
=back |
152 |
|
|
|
153 |
|
|
=head1 EXCEPTIONS |
154 |
|
|
|
155 |
root |
1.5 |
Guard blocks should not normally throw exceptions (that is, C<die>). After |
156 |
root |
1.1 |
all, they are usually used to clean up after such exceptions. However, if |
157 |
|
|
something truly exceptional is happening, a guard block should be allowed |
158 |
|
|
to die. Also, programming errors are a large source of exceptions, and the |
159 |
|
|
programmer certainly wants to know about those. |
160 |
|
|
|
161 |
|
|
Since in most cases, the block executing when the guard gets executes does |
162 |
|
|
not know or does not care about the guard blocks, it makes little sense to |
163 |
|
|
let containing code handle the exception. |
164 |
|
|
|
165 |
|
|
Therefore, whenever a guard block throws an exception, it will be caught, |
166 |
|
|
and this module will call the code reference stored in C<$Guard::DIED> |
167 |
|
|
(with C<$@> set to the actual exception), which is similar to how most |
168 |
|
|
event loops handle this case. |
169 |
|
|
|
170 |
|
|
The code reference stored in C<$Guard::DIED> should not die (behaviour is |
171 |
|
|
not guaranteed, but right now, the exception will simply be ignored). |
172 |
|
|
|
173 |
|
|
The default for C<$Guard::DIED> is to call C<warn "$@">. |
174 |
|
|
|
175 |
|
|
=head1 AUTHOR |
176 |
|
|
|
177 |
|
|
Marc Lehmann <schmorp@schmorp.de> |
178 |
|
|
http://home.schmorp.de/ |
179 |
|
|
|
180 |
|
|
=head1 THANKS |
181 |
|
|
|
182 |
root |
1.6 |
Thanks to Marco Maisenhelder, who reminded me of the C<$Guard::DIED> |
183 |
|
|
solution to the problem of exceptions. |
184 |
root |
1.1 |
|
185 |
|
|
=cut |
186 |
|
|
|