Key | Value |
---|---|
FileName | ./usr/share/man/man3/IO::InnerFile.3pm.gz |
FileSize | 1998 |
MD5 | C047EF09A2AE118E7FAAB69549DC682A |
SHA-1 | 05C04E66F8CDC7F78D3CA72E594412199AF61061 |
SHA-256 | 863E37B52D3414BAED1C6079B9D79086DF32A43D9F07435707C748E122609A4B |
SSDEEP | 48:XP+gKYBkhO+iJmBsylB/XwqcD+2Nd43M8jgd:bKcCOnmBsylq67M8j+ |
TLSH | T142412C74C9A32D02E463FD65B99C0347F527BF496C9875DB428A736C4C7409131EA01B |
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 | 1A5F0C0018B984672469800367647E7F |
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 | 1.fc22 |
PackageVersion | 2.111 |
SHA-1 | 1E2C49A0879C9B7493A5377ADB9CA627E2ECE9D3 |
SHA-256 | 2233D7F7D6E83940C62C80C2D02D345C2AFA0A76E4A2DBB99A52F077963E2608 |
Key | Value |
---|---|
MD5 | 41FEFFE1E45EA597F358EE74BB4E715A |
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 | 1.fc22 |
PackageVersion | 2.111 |
SHA-1 | E1A208EDA9DED4FFA3C298C997B353CBFA33468C |
SHA-256 | 55F22BD248535A5899CF1D474859C797D765AC3EC4BA131E7E1A41C7BAC73198 |
Key | Value |
---|---|
MD5 | 49BC9C971B4C3C091B18DB14F619B4F3 |
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 | 1.fc22 |
PackageVersion | 2.111 |
SHA-1 | 6F79E25FA09A3934FF7D984349D083068B3FA6A9 |
SHA-256 | 5EBF41A439FE2550E255081DB732E8880D337B16A0D8AB1C774D0E1C7AB81925 |