Key | Value |
---|---|
FileName | ./usr/share/man/man3/IO::Stringy.3pm.gz |
FileSize | 1940 |
MD5 | 1D6F3732536B7222901ABF730F29C603 |
SHA-1 | 677FB0A7CEBD5F9DAFA93DCE922B8A767B250951 |
SHA-256 | 535A95099FE64607509BD99AA338CF8775F1AB86BE5BA7611077CD8E032A6DA8 |
SSDEEP | 48:Xh5wtYysNEEa+ZYr7oo5kYbS9UdFUtSvZS:TwtYlal5nu9I+sM |
TLSH | T1CF41088DBD38D769C15031077F2E7E9CF1A7DB66D2B47EE0A81511E43A28860F2C8D42 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 8E69A682C57A75246F1DAC41B55F1723 |
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 which 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. |
PackageName | perl-IO-Stringy |
PackageRelease | 1.23 |
PackageVersion | 2.113 |
SHA-1 | 24BCE24B5F24BE4595CDFB89B10105A8A9AA2A9F |
SHA-256 | 2424F3E26AD804AB05C48F73C7DE4AB2A0DE7032E4D3D65285ADEED356EC4851 |