Packages / openSUSE Leap 15.6 / perl-Carp-Assert

Package: perl-Carp-Assert (0.22-bp156.1.1)

Executable comments

"We are ready for any unforseen event that may or may not occur." - Dan Quayle Carp::Assert is intended for a purpose like the ANSI C library at http://en.wikipedia.org/wiki/Assert.h. If you're already familiar with assert.h, then you can probably skip this and go straight to the FUNCTIONS section. Assertions are the explicit expressions of your assumptions about the reality your program is expected to deal with, and a declaration of those which it is not. They are used to prevent your program from blissfully processing garbage inputs (garbage in, garbage out becomes garbage in, error out) and to tell you when you've produced garbage output. (If I was going to be a cynic about Perl and the user nature, I'd say there are no user inputs but garbage, and Perl produces nothing but...) An assertion is used to prevent the impossible from being asked of your code, or at least tell you when it does. For example: sub my_sqrt { my($num) = shift; assert($num >= 0); return sqrt $num; } The assertion will warn you if a negative number was handed to your subroutine, a reality the routine has no intention of dealing with. An assertion should also be used as something of a reality check, to make sure what your code just did really did happen: open(FILE, $filename) || die $!; @stuff = <FILE>; @stuff = do_something(@stuff); assert(@stuff > 0); The assertion makes sure you have some @stuff at the end. Maybe the file was empty, maybe do_something() returned an empty list... either way, the assert() will give you a clue as to where the problem lies, rather than 50 lines down at when you wonder why your program isn't printing anything. Since assertions are designed for debugging and will remove themelves from production code, your assertions should be carefully crafted so as to not have any side-effects, change any variables, or otherwise have any effect on your program. Here is an example of a bad assertation: assert($error = 1 if $king ne 'Henry'); # Bad! It sets an error flag which may then be used somewhere else in your program. When you shut off your assertions with the $DEBUG flag, $error will no longer be set. Here's another example of *bad* use: assert($next_pres ne 'Dan Quayle' or goto Canada); # Bad! This assertion has the side effect of moving to Canada should it fail. This is a very bad assertion since error handling should not be placed in an assertion, nor should it have side-effects. In short, an assertion is an executable comment. For instance, instead of writing this $life = begin_life(); you'd replace the comment with an assertion which *enforces* the comment. $life = begin_life(); assert( $life =~ /!$/ );

Package information

Homepage
[https://metacpan.org/release/Carp-Assert]
License
Artistic-1.0 OR GPL-1.0-or-later
Downstream package maintainer
Unknown: not reported in the indexed source
Source package
[perl-Carp-Assert]
Software project
[libcarp-assert-perl]

Versions and downloads for perl-Carp-Assert

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
0.22-bp156.1.1leap-15.6 / ossnoarchopenSUSE Leap 15.6 · OSS · multi-architecture27 KiB27 KiBlist of filesperl-Carp-Assert-0.22-bp156.1.1.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-Carp-Assert

  • dep: perl(:MODULE_COMPAT_5.26.1)

    Package not available

Package file paths (7)

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.26.1/Carp
  • /usr/lib/perl5/vendor_perl/5.26.1/Carp/Assert.pm
  • /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi
  • /usr/share/doc/packages/perl-Carp-Assert
  • /usr/share/doc/packages/perl-Carp-Assert/Changes
  • /usr/share/doc/packages/perl-Carp-Assert/README
  • /usr/share/man/man3/Carp::Assert.3pm.gz

Field source: openSUSE Leap 15.6 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.22-bp156.1.1 / noarchObserved Sep 1, 2026sha512 b7a7aa37db7a…18f141f6Source-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): b7a7aa37db7a3925a8aac337456590611f91af0453079e864fff99319f0af0b56a5de0d54f1979a54b2c0514d9063aee9f4781fef05eecd79d6c445018f141f6

Field source: openSUSE Leap 15.6 OSS

Sources

  • Authoritative source; repository metadata signature verified

    Signature evidence

    leap-15-6-oss-multiarch:ca2653101b9afba6656aea529109ba0c0f1ca1a92aa8614e7c887fda5264c230

    Repository-signature verification record
    Signed-object SHA-256
    ca2653101b9afba6656aea529109ba0c0f1ca1a92aa8614e7c887fda5264c230
    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.