Key | Value |
---|---|
FileName | ./usr/share/man/man3/IO::Wrap.3pm.gz |
FileSize | 3720 |
MD5 | A007C16BB6E3BB92ED247AB260817194 |
SHA-1 | 244D1025C2724004E1A682F97E3C60D122D21CD7 |
SHA-256 | 2A57011B4B5CD39747572E240DEB58076766A1423038E35235B092923D46E6E3 |
SSDEEP | 96:mcVXH8RUM+MVheD8+o+iIc0rx8ZYcJhW3YXBYsaSKLLOJ:mu8aMR7RRhWI+BSKLLM |
TLSH | T11E717DF0E47ECF36A004E1223988E55900574ECCE6983DB761AA676861CDA4C4BC52E8 |
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 |