How to Install and Uninstall perl-String-Formatter Package on openSUSE Leap

Last updated: May 15,2024

1. Install "perl-String-Formatter" package

Please follow the steps below to install perl-String-Formatter on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-String-Formatter

2. Uninstall "perl-String-Formatter" package

Please follow the steps below to uninstall perl-String-Formatter on openSUSE Leap:

$ sudo zypper remove perl-String-Formatter

3. Information about the perl-String-Formatter package on openSUSE Leap

Information for package perl-String-Formatter:
----------------------------------------------
Repository : Main Repository
Name : perl-String-Formatter
Version : 1.235-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 70.6 KiB
Installed : No
Status : not installed
Source package : perl-String-Formatter-1.235-bp155.1.4.src
Upstream URL : https://metacpan.org/release/String-Formatter
Summary : Build sprintf-like functions of your own
Description :
String::Formatter is a tool for building sprintf-like formatting routines.
It supports named or positional formatting, custom conversions, fixed
string interpolation, and simple width-matching out of the box. It is easy
to alter its behavior to write new kinds of format string expanders. For
most cases, it should be easy to build all sorts of formatters out of the
options built into String::Formatter.
Normally, String::Formatter will be used to import a sprintf-like routine
referred to as "'stringf'", but which can be given any name you like. This
routine acts like sprintf in that it takes a string and some inputs and
returns a new string:
my $output = stringf "Some %a format %s for you to %u.\n", { ... };
This routine is actually a wrapper around a String::Formatter object
created by importing stringf. In the following code, the entire hashref
after "stringf" is passed to String::Formatter's constructor (the 'new'
method), save for the '-as' key and any other keys that start with a dash.
use String::Formatter
stringf => {
-as => 'fmt_time',
codes => { ... },
format_hunker => ...,
input_processor => ...,
},
stringf => {
-as => 'fmt_date',
codes => { ... },
string_replacer => ...,
hunk_formatter => ...,
},
;
As you can see, this will generate two stringf routines, with different
behaviors, which are installed with different names. Since the behavior of
these routines is based on the 'format' method of a String::Formatter
object, the rest of the documentation will describe the way the object
behaves.
There's also a 'named_stringf' export, which behaves just like the
'stringf' export, but defaults to the 'named_replace' and
'require_named_input' arguments. There's a 'method_stringf' export, which
defaults 'method_replace' and 'require_single_input'. Finally, a
'indexed_stringf', which defaults to 'indexed_replaced' and
'require_arrayref_input'. For more on these, keep reading, and check out
the cookbook.
String::Formatter::Cookbook provides a number of recipes for ways to put
String::Formatter to use.