Revision history for Scope-Upper
+0.09 2009-05-17 20:20 UTC
+ + Add : The new SU_THREADSAFE constant can be used to know whether the
+ module could have been built with thread safety enabled.
+ + Chg : Thread safety is disabled for perl 5.8 on Win32.
+ + Chg : A saner workaround for the "call_sv() during LEAVE clobbers the
+ still used last popped stack element" issue on 5.10.
+
0.08 2009-04-16 22:50 UTC
+ Fix : [RT #44204] : Stack corruption with reap(). Thanks Torsten
Foertsch for reporting.
--- #YAML:1.0
name: Scope-Upper
-version: 0.08
+version: 0.09
abstract: Act on upper scopes.
author:
- Vincent Pit <perl@profvince.com>
bugtracker: http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Scope-Upper
homepage: http://search.cpan.org/dist/Scope-Upper/
license: http://dev.perl.org/licenses/
- repository: http://git.profvince.com/?p=perl/modules/Scope-Upper.git
+ repository: http://git.profvince.com/?p=perl%2Fmodules%2FScope-Upper.git
no_index:
directory:
- t
Scope::Upper - Act on upper scopes.
VERSION
- Version 0.08
+ Version 0.09
SYNOPSIS
package X;
will righteously set $num to 26.
+CONSTANTS
+ "SU_THREADSAFE"
+ True iff the module could have been built when thread-safety features.
+
WORDS
Constants
"TOP"
"unwind" and "want_at" are only exported on request, either individually
or by the tags ':funcs' and ':all'.
+ The constant "SU_THREADSAFE" is also only exported on request,
+ individually or by the tags ':consts' and ':all'.
+
Same goes for the words "TOP", "HERE", "UP", "SUB", "EVAL", "SCOPE" and
"CALLER" that are only exported on request, individually or by the tags
':words' and ':all'.
=head1 VERSION
-Version 0.08
+Version 0.09
=cut
our $VERSION;
BEGIN {
- $VERSION = '0.08';
+ $VERSION = '0.09';
}
=head1 SYNOPSIS