-
perl-Devel-StackTrace-2.03-5.lbn25.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 25
-
perl-Devel-Symdump-2.17-3.fc25.noarch
The perl module Devel::Symdump provides a convenient way to inspect
perl's symbol table and the class hierarchy within a running program.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Digest-1.17-418.lbn25.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 depend of
the algorithm used. The message is simply a sequence of arbitrary
bytes or bits.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Digest-CRC-0.22.2-8.lbn25.x86_64
The Digest::CRC module calculates CRC sums of all sorts. It contains wrapper
functions with the correct parameters for CRC-CCITT, CRC-16 and CRC-32.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Digest-HMAC-1.03-20.lbn25.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 25
-
perl-Digest-MD5-2.55-418.lbn25.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 25
-
perl-Digest-SHA-6.02-5.lbn25.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 25
-
perl-Digest-SHA1-2.13-26.lbn25.x86_64
The Digest::SHA1 module allows you to use the NIST SHA-1 message
digest algorithm from within Perl programs. The algorithm takes as
input a message of arbitrary length and produces as output a 160-bit
"fingerprint" or "message digest" of the input.
The Digest::SHA1 module provide a procedural interface for simple use,
as well as an object oriented interface that can handle messages of
arbitrary length and which can read files directly.
A binary digest will be 20 bytes long. A hex digest will be 40
characters long. A base64 digest will be 27 characters long.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Dir-Self-0.11-12.lbn25.noarch
Perl has two pseudo-constants describing the current location in your
source code, __FILE__ and __LINE__. This module adds __DIR__, which expands
to the directory your source file is in, as an absolute pathname.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 25
-
perl-Dist-CheckConflicts-0.11-14.lbn25.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 25
