liblexical-failure-perl 0.001001-1 source package in Ubuntu
Changelog
liblexical-failure-perl (0.001001-1) unstable; urgency=medium
* Team upload.
* Import upstream version 0.001001.
Fixes "FTBFS with Perl 5.38: test failures"
(Closes: #1042852)
* Declare compliance with Debian Policy 4.6.2.
* Set Rules-Requires-Root: no.
* Drop unversioned 'perl' from Depends.
* Annotate test-only build dependencies with <!nocheck>.
-- gregor herrmann <email address hidden> Wed, 02 Aug 2023 00:41:47 +0200
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | release | universe | misc | |
| Noble | release | universe | misc | |
| Mantic | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| liblexical-failure-perl_0.001001-1.dsc | 2.5 KiB | 2987560ff38f3bc0d41d05ed163241871d7e7292c011294a2f1349a5bed57228 |
| liblexical-failure-perl_0.001001.orig.tar.gz | 17.3 KiB | 9a0ab3b25882bd0f46498aa9add3139e1209d2607101636857cc615342fb3a45 |
| liblexical-failure-perl_0.001001-1.debian.tar.xz | 2.5 KiB | 446dc921c14f6c02598643340c7f0ff9567040cae527bbe491057dcdbb1bd191 |
Available diffs
- diff from 0.000007-3 to 0.001001-1 (5.8 KiB)
No changes file available.
Binary packages built by this source
- liblexical-failure-perl: 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.
