Key | Value |
---|---|
FileName | ./usr/share/man/man3/IO::Lines.3pm.gz |
FileSize | 1865 |
MD5 | 6492D73525621A9C1D8C7F491BAAC03E |
SHA-1 | 68C6811D1726524E8DBB03F1C4B13923FBCC0237 |
SHA-256 | 674E80FDC1DBD291EE21DC688611F161A744FF2E0E8DCDD0FD54C9560E6BA98C |
SSDEEP | 48:XktBJ08vB1Z8nrGUMXMV7Cj/KoNfiEtv479iPoyH:iFvBLtuCjyjOQ2H |
TLSH | T16731FBA5CA15E86085A44CB197AC79733D7A46C771B0AFF0D3BBD291B5412022DB446B |
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 |