How to Install and Uninstall liblexical-failure-perl Package on Ubuntu 21.10 (Impish Indri)
Last updated: November 05,2024
1. Install "liblexical-failure-perl" package
This is a short guide on how to install liblexical-failure-perl on Ubuntu 21.10 (Impish Indri)
$
sudo apt update
Copied
$
sudo apt install
liblexical-failure-perl
Copied
2. Uninstall "liblexical-failure-perl" package
Please follow the step by step instructions below to uninstall liblexical-failure-perl on Ubuntu 21.10 (Impish Indri):
$
sudo apt remove
liblexical-failure-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the liblexical-failure-perl package on Ubuntu 21.10 (Impish Indri)
Package: liblexical-failure-perl
Architecture: all
Version: 0.000007-2.1
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 71
Depends: perl:any, libkeyword-simple-perl, libscope-upper-perl, perl (>= 5.14.0)
Filename: pool/universe/libl/liblexical-failure-perl/liblexical-failure-perl_0.000007-2.1_all.deb
Size: 26528
MD5sum: b19f1c3acfe4f52289b3f5a24da4dff0
SHA1: 38f4d2eb9532342f8a1fd8a32cbeeae19fcb2f63
SHA256: 722438830c2d5dd7a808db78547e6057283153139a745d56aebd4ff5ca9ca300
SHA512: 379285b51014801d428263e7de8d748f35f761bde88aaf45398c8f6e1e35d44781d144f98ec385461831dedbcb76eb57f9814e4c8fed463eee71916604905f3a
Homepage: https://metacpan.org/release/Lexical-Failure
Description-en: Perl module for user-selectable lexically-scoped failure signaling
Lexical::Failure sets up two new keywords: fail and ON_FAILURE, with which
you can quickly create modules whose failure signaling is lexcially scoped,
under the control of client code.
.
Normally, modules specify some fixed mechanism for error handling and require
client code to adapt to that policy. One module may signal errors by
returning undef, or perhaps some special "error object". Another may die or
croak on failure. A third may set a flag variable. A fourth may require the
client code to set up a callback, which is executed on failure.
.
If you are using all four modules, your own code now has to check for failure
in four different ways, depending on where the failing component originated.
If you would rather that all components throw exceptions, or all return
undef, you will probably have to write wrappers around 3/4 of them, to
convert from their "native" failure mechanism to your preferred one.
Description-md5: 9c8be0534036c5a3221fa83ce4b15991
Architecture: all
Version: 0.000007-2.1
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 71
Depends: perl:any, libkeyword-simple-perl, libscope-upper-perl, perl (>= 5.14.0)
Filename: pool/universe/libl/liblexical-failure-perl/liblexical-failure-perl_0.000007-2.1_all.deb
Size: 26528
MD5sum: b19f1c3acfe4f52289b3f5a24da4dff0
SHA1: 38f4d2eb9532342f8a1fd8a32cbeeae19fcb2f63
SHA256: 722438830c2d5dd7a808db78547e6057283153139a745d56aebd4ff5ca9ca300
SHA512: 379285b51014801d428263e7de8d748f35f761bde88aaf45398c8f6e1e35d44781d144f98ec385461831dedbcb76eb57f9814e4c8fed463eee71916604905f3a
Homepage: https://metacpan.org/release/Lexical-Failure
Description-en: Perl module for user-selectable lexically-scoped failure signaling
Lexical::Failure sets up two new keywords: fail and ON_FAILURE, with which
you can quickly create modules whose failure signaling is lexcially scoped,
under the control of client code.
.
Normally, modules specify some fixed mechanism for error handling and require
client code to adapt to that policy. One module may signal errors by
returning undef, or perhaps some special "error object". Another may die or
croak on failure. A third may set a flag variable. A fourth may require the
client code to set up a callback, which is executed on failure.
.
If you are using all four modules, your own code now has to check for failure
in four different ways, depending on where the failing component originated.
If you would rather that all components throw exceptions, or all return
undef, you will probably have to write wrappers around 3/4 of them, to
convert from their "native" failure mechanism to your preferred one.
Description-md5: 9c8be0534036c5a3221fa83ce4b15991