X-Git-Url: http://git.vpit.fr/?a=blobdiff_plain;ds=sidebyside;f=lib%2FScope%2FUpper.pm;h=84de02eea6ebf8befe98320881ff7d27f3d421fa;hb=44bbbdcdafa5707a753abb9de5c5d01cd7388880;hp=6d1616be401cea136cc5b304f202cf4d566aa5bd;hpb=43294f5e9bafd1f0bdeaa89d9d20335f08f1f050;p=perl%2Fmodules%2FScope-Upper.git
diff --git a/lib/Scope/Upper.pm b/lib/Scope/Upper.pm
index 6d1616b..84de02e 100644
--- a/lib/Scope/Upper.pm
+++ b/lib/Scope/Upper.pm
@@ -9,13 +9,13 @@ Scope::Upper - Act on upper scopes.
=head1 VERSION
-Version 0.09
+Version 0.10
=cut
our $VERSION;
BEGIN {
- $VERSION = '0.09';
+ $VERSION = '0.10';
}
=head1 SYNOPSIS
@@ -144,11 +144,27 @@ will set C<$x> to a reference to the string C<'foo'>.
Other sigils (C<'@'>, C<'%'>, C<'&'> and C<'*'>) require C<$value> to be a reference of the corresponding type.
When the symbol is given by a string, it is resolved when the actual localization takes place and not when C is called.
-This means that
+Thus, if the symbol name is not qualified, it will refer to the variable in the package where the localization actually takes place and not in the one where the C call was compiled.
+For example,
- sub tag { localize '$x', $_[0] => UP }
+ {
+ package Scope;
+ sub new { localize '$tag', $_[0] => UP }
+ }
-will localize in the caller's namespace.
+ {
+ package Tool;
+ {
+ Scope->new;
+ ...
+ }
+ }
+
+will localize C<$Tool::tag> and not C<$Scope::tag>.
+
+Note that if C<$what> is a string denoting a variable that wasn't declared beforehand, the relevant slot will be vivified as needed and won't be deleted from the glob when the localization ends.
+This situation never arises with C because it only compiles when the localized variable is already declared.
+Although I believe it shouldn't be a problem as glob slots definedness is pretty much an implementation detail, this behaviour may change in the future if proved harmful.
=back
@@ -158,6 +174,8 @@ Similar to L but for array and hash elements.
If C<$what> is a glob, the slot to fill is determined from which type of reference C<$value> is ; otherwise it's inferred from the sigil.
C<$key> is either an array index or a hash key, depending of which kind of variable you localize.
+Just like for L, when C<$what> is a string pointing to an undeclared variable, it will be vivified but the variable itself will be empty when the localization ends (although it will still exist in its parent glob).
+
=head2 C
Similiar to L, but for deleting variables or array/hash elements.
@@ -389,7 +407,8 @@ You can contact me by mail or on C (vincent).
=head1 BUGS
-Please report any bugs or feature requests to C, or through the web interface at L. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
+Please report any bugs or feature requests to C, or through the web interface at L.
+I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
=head1 SUPPORT