-
perl-Devel-Declare-0.006011-4.fc19.x86_64
Devel::Declare can install subroutines called declarators which locally
take over Perl's parser, allowing the creation of new syntax.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
perl-Devel-FindRef-1.42-19.fc19.x86_64
Tracking down reference problems (e.g. you expect some object to be
destroyed, but there are still references to it that keep it alive) can be
very hard. Fortunately, perl keeps track of all its values, so tracking
references "backwards" is usually possible.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
perl-Devel-GlobalDestruction-0.11-1.fc19.noarch
Perl's global destruction is a little tricky to deal with with respect to
finalizers because it's not ordered and objects can sometimes disappear.
Writing defensive destructors is hard and annoying, and usually if global
destruction is happening you only need the destructors that free up non
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if
global destruction is in effect.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
perl-Devel-GlobalDestruction-0.14-8.lbn25.noarch
Perl's global destruction is a little tricky to deal with with respect to
finalizers because it's not ordered and objects can sometimes disappear.
Writing defensive destructors is hard and annoying, and usually if global
destruction is happening you only need the destructors that free up non
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if
global destruction is in effect.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Devel-GlobalDestruction-0.14-17.fc36.noarch
Perl's global destruction is a little tricky to deal with with respect to
finalizers because it's not ordered and objects can sometimes disappear.
Writing defensive destructors is hard and annoying, and usually if global
destruction is happening you only need the destructors that free up non
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if
global destruction is in effect.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Devel-GlobalDestruction-0.02-8.lbn13.x86_64
Perl's global destruction is a little tricky to deal with with respect to
finalizers because it's not ordered and objects can sometimes disappear.
Writing defensive destructors is hard and annoying, and usually if global
destruction is happenning you only need the destructors that free up non
process local resources to actually execute.
For these constructors you can avoid the mess by simply bailing out if
global destruction is in effect.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 13
-
perl-Devel-Hide-0.0009-1.fc19.noarch
Given a list of Perl modules/filenames, this module makes require and
use statements fail (no matter the specified files/modules are
installed or not).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
perl-Devel-Hide-0.0010-4.lbn25.noarch
Given a list of Perl modules/filenames, this module makes require and use
statements fail (regardless of whether the specified files/modules are
installed or not).
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Devel-Leak-0.03-21.lbn19.armv6hl
This module provides a basic way to discover if a piece of perl code
is allocating perl data and not releasing them again.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
perl-Devel-Leak-0.03-21.fc19.x86_64
This module provides a basic way to discover if a piece of perl code
is allocating perl data and not releasing them again.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
