How to Install and Uninstall perl-List-BinarySearch Package on openSUSE Leap
Last updated: November 23,2024
1. Install "perl-List-BinarySearch" package
Please follow the step by step instructions below to install perl-List-BinarySearch on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-List-BinarySearch
Copied
2. Uninstall "perl-List-BinarySearch" package
Here is a brief guide to show you how to uninstall perl-List-BinarySearch on openSUSE Leap:
$
sudo zypper remove
perl-List-BinarySearch
Copied
3. Information about the perl-List-BinarySearch package on openSUSE Leap
Information for package perl-List-BinarySearch:
-----------------------------------------------
Repository : Main Repository
Name : perl-List-BinarySearch
Version : 0.25-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 44.9 KiB
Installed : No
Status : not installed
Source package : perl-List-BinarySearch-0.25-bp155.1.4.src
Upstream URL : https://metacpan.org/release/List-BinarySearch
Summary : Binary Search within a sorted array.
Description :
A binary search searches *sorted* lists using a divide and conquer
technique. On each iteration the search domain is cut in half, until the
result is found. The computational complexity of a binary search is
O(log n).
The binary search algorithm implemented in this module is known as a
_Deferred Detection_ variant on the traditional Binary Search. Deferred
Detection provides *stable searches*. Stable binary search algorithms have
the following characteristics, contrasted with their unstable binary search
cousins:
* In the case of non-unique keys, a stable binary search will always
return the lowest-indexed matching element. An unstable binary search
would return the first one found, which may not be the chronological first.
* Best and worst case time complexity is always O(log n). Unstable
searches may stop once the target is found, but in the worst case are
still O(log n). In practical terms, this difference is usually not
meaningful.
* Stable binary searches only require one relational comparison of a
given pair of data elements per iteration, where unstable binary searches
require two comparisons per iteration.
* The net result is that although an unstable binary search might have
better "best case" performance, the fact that a stable binary search gets
away with fewer comparisons per iteration gives it better performance in the
worst case, and approximately equal performance in the average case. By
trading away slightly better "best case" performance, the stable search gains
the guarantee that the element found will always be the lowest-indexed
element in a range of non-unique keys.
This module has a companion "XS" module: the List::BinarySearch::XS
manpage which users are strongly encouraged to install as well. If
List::BinarySearch::XS is also installed, 'binsearch' and 'binsearch_pos'
will use XS code. This behavior may be overridden by setting
'$ENV{List_BinarySearch_PP}' to a true value. Most CPAN installers will
either automatically install the XS module, or prompt to automatically
install it. See CONFIGURATION for details.
-----------------------------------------------
Repository : Main Repository
Name : perl-List-BinarySearch
Version : 0.25-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 44.9 KiB
Installed : No
Status : not installed
Source package : perl-List-BinarySearch-0.25-bp155.1.4.src
Upstream URL : https://metacpan.org/release/List-BinarySearch
Summary : Binary Search within a sorted array.
Description :
A binary search searches *sorted* lists using a divide and conquer
technique. On each iteration the search domain is cut in half, until the
result is found. The computational complexity of a binary search is
O(log n).
The binary search algorithm implemented in this module is known as a
_Deferred Detection_ variant on the traditional Binary Search. Deferred
Detection provides *stable searches*. Stable binary search algorithms have
the following characteristics, contrasted with their unstable binary search
cousins:
* In the case of non-unique keys, a stable binary search will always
return the lowest-indexed matching element. An unstable binary search
would return the first one found, which may not be the chronological first.
* Best and worst case time complexity is always O(log n). Unstable
searches may stop once the target is found, but in the worst case are
still O(log n). In practical terms, this difference is usually not
meaningful.
* Stable binary searches only require one relational comparison of a
given pair of data elements per iteration, where unstable binary searches
require two comparisons per iteration.
* The net result is that although an unstable binary search might have
better "best case" performance, the fact that a stable binary search gets
away with fewer comparisons per iteration gives it better performance in the
worst case, and approximately equal performance in the average case. By
trading away slightly better "best case" performance, the stable search gains
the guarantee that the element found will always be the lowest-indexed
element in a range of non-unique keys.
This module has a companion "XS" module: the List::BinarySearch::XS
manpage which users are strongly encouraged to install as well. If
List::BinarySearch::XS is also installed, 'binsearch' and 'binsearch_pos'
will use XS code. This behavior may be overridden by setting
'$ENV{List_BinarySearch_PP}' to a true value. Most CPAN installers will
either automatically install the XS module, or prompt to automatically
install it. See CONFIGURATION for details.