Key | Value |
---|---|
FileName | ./usr/share/doc/perl-IO-stringy/README |
FileSize | 1709 |
MD5 | D93ACD3D344930738560559FDCB331B7 |
SHA-1 | 09D9E285F0FE6249AF54F06633E88D28873B328B |
SHA-256 | C9576A5AA5F47C4533A0508F993EA447FEF216F5EDA868BBE6C583B3797E3338 |
SSDEEP | 24:8KwYo1omXhw3gcJgFRg3gaN5z+ixfqW0+JDiQ1Ww+Z0Ya2HgTPFk7HZZNnMj:Rw6+w3gFowsK8qH2OizMo2Hg7FqZZJY |
TLSH | T1F931561EB607526B020241619396EE72D84192EB254132F5F52D835B1F67D2C62FBFFC |
hashlookup:parent-total | 21 |
hashlookup:trust | 100 |
The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 2AD5FF0B2C8661D6A72E805B20A6C152 |
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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | perl-IO-stringy |
PackageRelease | 1.9 |
PackageVersion | 2.113 |
SHA-1 | 0800F791DFEE9BCBF25AD47C87B602D9B7E98031 |
SHA-256 | 5E8F61B4255AD26A50523169E0AB6B7D692CA83717D6961D33445D021568AC60 |
Key | Value |
---|---|
MD5 | 192ABAA86746F86346AD381E7AF28B6B |
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 | lp152.315.2 |
PackageVersion | 2.113 |
SHA-1 | 0D679373A977612975A5CE71C52776AC6C1D1E18 |
SHA-256 | AF46EBE6F063105CC2D8FB4642151FA8567848B65CF68BC5D04471D43951EC20 |
Key | Value |
---|---|
MD5 | 85A3376B625FC7C5BA4E8FFE6F235FE7 |
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, the IO::Scalar manpage, the IO::ScalarArray manpage, and the IO::Lines manpage. If you have access to tie(), these classes will make use of the the IO::WrapTie manpage module to inherit a convenient new_tie() constructor. It also exports a nice wraptie() function. In the more-traditional IO::Handle front, we have the IO::AtomicFile manpage which may be used to painlessly create files which are updated atomically. And in the "this-may-prove-useful" corner, we have the IO::Wrap manpage, 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 | umeabot <umeabot> |
PackageName | perl-IO-stringy |
PackageRelease | 2.mga9 |
PackageVersion | 2.113.0 |
SHA-1 | 123D346466D3392D66ABC14C9BE00159066C04BC |
SHA-256 | 888B553D4FE78510AB32D9B234AF7A7B3BD796C757D8A5F9C9C613D02319DE26 |
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 |
Key | Value |
---|---|
MD5 | 06379BB46F35C96285DD7F55E30C89EC |
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 | 3.2 |
PackageVersion | 2.113 |
SHA-1 | 266DDE836EF63B70CF5C75390E0E2CC19CC31809 |
SHA-256 | 756E785861233FB0F25CF23F0572E2D1175DFA838209A43B572C765F428E8754 |
Key | Value |
---|---|
MD5 | 3D85A7488BB770C5BE8C079F283854FD |
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 | 315.2 |
PackageVersion | 2.113 |
SHA-1 | 314620AB00A0E1F98FBE427C4D4F69CC1366B748 |
SHA-256 | 57A3A6FAC5C0AEA60E62DE55558360F2FF417814DFCA624F41DF8959C75C970C |
Key | Value |
---|---|
MD5 | 844D3CDA821818FD2BBE1DA2186A41C3 |
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 | lp153.315.12 |
PackageVersion | 2.113 |
SHA-1 | 43D41E0741CBBE6D0D4D12D8EAE285EA4A69E92A |
SHA-256 | 44F6D1AB3979238648FF05B23EA01636B9ECD296840B2AADBC94FFBD358D8545 |
Key | Value |
---|---|
MD5 | 3EB4C2E4372F70C671CAAF7CB994D086 |
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 | 315.1 |
PackageVersion | 2.113 |
SHA-1 | 559B004CDCC07742E571791C6F2365D4FE94A591 |
SHA-256 | 3F85315630927709AF893DCC94722FAA198F2A4C35E29B0E25B71EF566F58BC5 |
Key | Value |
---|---|
MD5 | C9627C21A671554F1D64DA94E6ACF365 |
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 | 4.fc33 |
PackageVersion | 2.113 |
SHA-1 | 5BB62B35E4EB674623086669637B9AB114173E5C |
SHA-256 | 4F5CA36A084CC914BFFD46CB7D208BC9BD29F82AA4287690D91F4A0754020CD8 |
Key | Value |
---|---|
MD5 | 7C8C0B016F842B409242483C0423303C |
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 | 315.32 |
PackageVersion | 2.113 |
SHA-1 | 66F48AEE35A4E027C368B90946426F1AEFC6CB19 |
SHA-256 | 3A3464ED18A76410D506791F269BEDC46F485958A2A7AFC3BECE2E0016C8428C |