How to Install and Uninstall perl-Try-Tiny Package on openSuSE Tumbleweed

Last updated: May 17,2024

1. Install "perl-Try-Tiny" package

In this section, we are going to explain the necessary steps to install perl-Try-Tiny on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install perl-Try-Tiny

2. Uninstall "perl-Try-Tiny" package

In this section, we are going to explain the necessary steps to uninstall perl-Try-Tiny on openSuSE Tumbleweed:

$ sudo zypper remove perl-Try-Tiny

3. Information about the perl-Try-Tiny package on openSuSE Tumbleweed

Information for package perl-Try-Tiny:
--------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-Try-Tiny
Version : 0.31-1.11
Arch : noarch
Vendor : openSUSE
Installed Size : 37.4 KiB
Installed : No
Status : not installed
Source package : perl-Try-Tiny-0.31-1.11.src
Upstream URL : https://metacpan.org/release/Try-Tiny
Summary : Minimal try/catch with proper preservation of $@
Description :
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.