Key | Value |
---|---|
FileName | ./usr/share/man/man3/IO::Stringy.3pm.gz |
FileSize | 7468 |
MD5 | FC398F406B21ED6223A91FA5F9D6C19C |
SHA-1 | 3F8F1C20A9FF3AD5107CCCA5B19AD5063DE331BE |
SHA-256 | 8D3E3F47234C37D00CDCB62F119BFF24E614476E9B8DCC4622A8B6A27CBD7EAA |
SSDEEP | 192:elSXCvNeDUH12fj/Vfsrovbw148U6xdms3XDL:ekXTAUfp2TIEd93XH |
TLSH | T138F19DA12E154B6E4C66D3D99E10E50FFACDF093C62D58BB201D1E60B039E886B7493F |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 3F3C471ACEBF108F183CE429D6D33A62 |
PackageArch | noarch |
PackageDescription | This toolkit primarily provides modules for performing both traditional and object-oriented I/O) on things *other* than normal filehandles; in particular, IO::Scalar, IO::ScalarArray, and IO::Lines. In the more-traditional IO::Handle front, we have IO::AtomicFile, which may be used to painlessly create files that are updated atomically. And in the "this-may-prove-useful" corner, we have IO::Wrap, whose exported wraphandle() function will clothe anything that's not a blessed object in an IO::Handle-like wrapper... so you can just use OO syntax and stop worrying about whether your function's caller handed you a string, a globref, or a FileHandle. |
PackageMaintainer | Fedora Project |
PackageName | perl-IO-stringy |
PackageRelease | 22.fc19 |
PackageVersion | 2.110 |
SHA-1 | 15DA8B8953FCF47885AF61199520ABCDB1A00797 |
SHA-256 | 239CFED57DE73D9B472898F8CDCEDE8D0F114B03D981BA9684D3FF18A62791AC |
Key | Value |
---|---|
MD5 | 4F60992A2DB556799DDD9B297F55755E |
PackageArch | noarch |
PackageDescription | This toolkit primarily provides modules for performing both traditional and object-oriented I/O) on things *other* than normal filehandles; in particular, IO::Scalar, IO::ScalarArray, and IO::Lines. In the more-traditional IO::Handle front, we have IO::AtomicFile, which may be used to painlessly create files that are updated atomically. And in the "this-may-prove-useful" corner, we have IO::Wrap, whose exported wraphandle() function will clothe anything that's not a blessed object in an IO::Handle-like wrapper... so you can just use OO syntax and stop worrying about whether your function's caller handed you a string, a globref, or a FileHandle. |
PackageMaintainer | Fedora Project |
PackageName | perl-IO-stringy |
PackageRelease | 22.fc19 |
PackageVersion | 2.110 |
SHA-1 | E7C8A126E74545B40E4D6B1917AB4C54ADDCF4A1 |
SHA-256 | DA30BB08C327D7F9F4C470ACEB7AE5ECFC4F2D6734A13AFB78E9B788A56FC8A3 |
Key | Value |
---|---|
MD5 | 29534571112ED9256D1461C7667ECAED |
PackageArch | noarch |
PackageDescription | This toolkit primarily provides modules for performing both traditional and object-oriented I/O) on things *other* than normal filehandles; in particular, IO::Scalar, IO::ScalarArray, and IO::Lines. In the more-traditional IO::Handle front, we have IO::AtomicFile, which may be used to painlessly create files that are updated atomically. And in the "this-may-prove-useful" corner, we have IO::Wrap, whose exported wraphandle() function will clothe anything that's not a blessed object in an IO::Handle-like wrapper... so you can just use OO syntax and stop worrying about whether your function's caller handed you a string, a globref, or a FileHandle. |
PackageMaintainer | Fedora Project |
PackageName | perl-IO-stringy |
PackageRelease | 22.fc19 |
PackageVersion | 2.110 |
SHA-1 | 09BE51737B2BC02E6EFDD5C68A75EAA81B81B2A5 |
SHA-256 | 8A0CDAD63DFA2A8FD4C1B649F2393435A5C7DA06AAAA70FDEB4773057DDD94AB |