Packages / openSUSE Leap 16.0 / perl-Try-Tiny

Package: perl-Try-Tiny (0.31-160000.2.2)

Minimal try/catch with proper preservation of $@

This module provides bare bones 'try'/'catch'/'finally' statements that are designed to minimize common mistakes with eval blocks, and NOTHING else. This is unlike TryCatch which provides a nice syntax and avoids adding another call stack layer, and supports calling 'return' from the 'try' block to return from the parent subroutine. These extra features come at a cost of a few dependencies, namely Devel::Declare and Scope::Upper which are occasionally problematic, and the additional catch filtering uses Moose type constraints which may not be desirable either. The main focus of this module is to provide simple and reliable error handling for those having a hard time installing TryCatch, but who still want to write correct 'eval' blocks without 5 lines of boilerplate each time. It's designed to work as correctly as possible in light of the various pathological edge cases (see BACKGROUND) and to be compatible with any style of error values (simple strings, references, objects, overloaded objects, etc). If the 'try' block dies, it returns the value of the last statement executed in the 'catch' block, if there is one. Otherwise, it returns 'undef' in scalar context or the empty list in list context. The following examples all assign '"bar"' to '$x': my $x = try { die "foo" } catch { "bar" }; my $x = try { die "foo" } || "bar"; my $x = (try { die "foo" }) // "bar"; my $x = eval { die "foo" } || "bar"; You can add 'finally' blocks, yielding the following: my $x; try { die 'foo' } finally { $x = 'bar' }; try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' }; 'finally' blocks are always executed making them suitable for cleanup code which cannot be handled using local. You can add as many 'finally' blocks to a given 'try' block as you like. Note that adding a 'finally' block without a preceding 'catch' block suppresses any errors. This behaviour is consistent with using a standalone 'eval', but it is not consistent with 'try'/'finally' patterns found in other programming languages, such as Java, Python, Javascript or C#. If you learned the 'try'/'finally' pattern from one of these languages, watch out for this.

Package information

Homepage
[https://metacpan.org/release/Try-Tiny]
License
MIT
Downstream package maintainer
Unknown: not reported in the indexed source
Source package
[perl-Try-Tiny]
Software project
[perl-try-tiny]

Versions and downloads for perl-Try-Tiny

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
0.31-160000.2.2leap-16.0 / ossnoarchopenSUSE Leap 16.0 · OSS · multi-architecture34 KiB37 KiBlist of filesperl-Try-Tiny-0.31-160000.2.2.noarch.rpm
About these downloads

Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.

Dependencies and recommendations for perl-Try-Tiny

  • dep: perl(:MODULE_COMPAT_5.42.0)

    Package not available

Package file paths (9)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /usr/lib/perl5/vendor_perl/5.42.0/Try
  • /usr/lib/perl5/vendor_perl/5.42.0/Try/Tiny.pm
  • /usr/share/doc/packages/perl-Try-Tiny
  • /usr/share/doc/packages/perl-Try-Tiny/Changes
  • /usr/share/doc/packages/perl-Try-Tiny/CONTRIBUTING
  • /usr/share/doc/packages/perl-Try-Tiny/README
  • /usr/share/licenses/perl-Try-Tiny
  • /usr/share/licenses/perl-Try-Tiny/LICENCE
  • /usr/share/man/man3/Try::Tiny.3pm.gz

Field source: openSUSE Leap 16.0 OSS

Known vulnerabilities

No matching advisories in the tracked sources.

Last synced:

[CVE catalog]

Checksums

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

0.31-160000.2.2 / noarchObserved Sep 1, 2026sha512 46d8975931e4…b1e4080cSource-reported digest

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Source-reported digest (sha512): 46d8975931e48d54f1d83ddf78be7e9e04fa33463cc6b6bb86bbf1b948068cf44f00411a72cda8b8ef8c0e2b5b7dd93a365fda0de1fc4d53b93a6f73b1e4080c

Field source: openSUSE Leap 16.0 OSS

Sources

  • Authoritative source; repository metadata signature verified

    Signature evidence

    leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

    Repository-signature verification record
    Signed-object SHA-256
    271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable

Use this package

OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.