-
perl-Devel-LexAlias-0.05-28.fc36.x86_64
Devel::LexAlias provides the ability to alias a lexical variable in a
subroutines scope to one of your choosing.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Devel-Peek-1.30-486.fc36.x86_64
Devel::Peek contains functions which allows raw Perl data types to be
manipulated from a Perl script. This is used by those who do XS programming to
check that the data they are sending from C to Perl looks as they think it
should look.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Devel-SelfStubber-1.06-486.fc36.noarch
Devel::SelfStubber prints the stubs you need to put in the module before the
__DATA__ token (or you can get it to print the entire module with stubs
correctly placed). The stubs ensure that if a method is called, it will get
loaded. They are needed specifically for inherited autoloaded methods.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Devel-StackTrace-2.05-4.lbn36.noarch
The Devel::StackTrace module contains two classes, Devel::StackTrace
and Devel::StackTraceFrame. The goal of this object is to encapsulate
the information that can found through using the caller() function, as
well as providing a simple interface to this data.
The Devel::StackTrace object contains a set of Devel::StackTraceFrame
objects, one for each level of the stack. The frames contain all the
data available from caller() as of Perl 5.6.0.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Digest-1.20-2.fc36.noarch
The Digest:: modules calculate digests, also called "fingerprints" or
"hashes", of some data, called a message. The digest is (usually) some
small/fixed size string. The actual size of the digest depends of the
algorithm used. The message is simply a sequence of arbitrary bytes or bits.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Digest-HMAC-1.04-4.fc36.noarch
HMAC is used for message integrity checks between two parties that
share a secret key, and works in combination with some other Digest
algorithm, usually MD5 or SHA-1. The HMAC mechanism is described in
RFC 2104.
HMAC follow the common Digest:: interface, but the constructor takes
the secret key and the name of some other simple Digest:: as argument.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Digest-MD5-2.58-479.fc36.x86_64
The Digest::MD5 module allows you to use the RSA Data Security Inc. MD5
Message Digest algorithm from within Perl programs. The algorithm takes as
input a message of arbitrary length and produces as output a 128-bit
"fingerprint" or "message digest" of the input.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Digest-SHA-6.03-1.fc36.x86_64
Digest::SHA is a complete implementation of the NIST Secure Hash Standard. It
gives Perl programmers a convenient way to calculate SHA-1, SHA-224, SHA-256,
SHA-384, SHA-512, SHA-512/224, and SHA-512/256 message digests. The module can
handle all types of input, including partial-byte data.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-DirHandle-1.05-486.fc36.noarch
There is no reason to use this module nowadays. The DirHandle module provides
an alternative interface to the opendir(), closedir(), readdir(), and
rewinddir() functions. Since Perl 5.6, opendir() alone has been all you need
for lexical handles.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
-
perl-Dist-CheckConflicts-0.11-24.fc36.noarch
One shortcoming of the CPAN clients that currently exist is that they have no
way of specifying conflicting downstream dependencies of modules. This module
attempts to work around this issue by allowing you to specify conflicting
versions of modules separately, and deal with them after the module is done
installing.
For instance, say you have a module Foo, and some other module Bar uses Foo. If
Foo were to change its API in a non-backwards-compatible way, this would cause
Bar to break until it is updated to use the new API. Foo can't just depend on
the fixed version of Bar, because this will cause a circular dependency
(because Bar is already depending on Foo), and this doesn't express intent
properly anyway - Foo doesn't use Bar at all. The ideal solution would be for
there to be a way to specify conflicting versions of modules in a way that would
let CPAN clients update conflicting modules automatically after an existing
module is upgraded, but until that happens, this module will allow users to do
this manually.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 36
