| Key | Value |
|---|---|
| FileName | ./usr/share/man/man3/Data::OptList.3pm.gz |
| FileSize | 3071 |
| MD5 | 65CF4C0F969E7850D986EDD8495CE573 |
| SHA-1 | 26525B451ACDC5E194FF58831A41500AF3664106 |
| SHA-256 | E24F6D2A7863D9E80E1F0BFA2AED4F26D3C5F2F752A2E35B8C3A21BD821E5C2A |
| SSDEEP | 48:XAIuYIFrSdRv8SakgYZjf/BO9gGm5P7TCMUnIOwHZ9dvZMKtMgoWsurp:QIQSdRv8Z3Gb3GmV7uMFrZKEMB6 |
| TLSH | T186514BF16C6BC45058F2FC9C424C8D0E8F5B59C05B794B72B8C9C3E5A6A28E4694D322 |
| hashlookup:parent-total | 5 |
| hashlookup:trust | 75 |
The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 34EA53DF66803051059969A60C574E11 |
| PackageArch | noarch |
| PackageDescription | Hashes are great for storing named data, but if you want more than one entry for a name, you have to use a list of pairs. Even then, this is really boring to write: $values = [ foo => undef, bar => undef, baz => undef, xyz => { ... }, ]; Just look at all those undefs! Don't worry, we can get rid of those: $values = [ map { $_ => undef } qw(foo bar baz), xyz => { ... }, ]; Aaaauuugh! We've saved a little typing, but now it requires thought to read, and thinking is even worse than typing... and it's got a bug! It looked right, didn't it? Well, the 'xyz => { ... }' gets consumed by the map, and we don't get the data we wanted. With Data::OptList, you can do this instead: $values = Data::OptList::mkopt([ qw(foo bar baz), xyz => { ... }, ]); This works by assuming that any defined scalar is a name and any reference following a name is its value. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | perl-Data-OptList |
| PackageRelease | lp150.1.3 |
| PackageVersion | 0.110 |
| SHA-1 | 2F5199E90369E25BE51582133F61FE5576B95566 |
| SHA-256 | 7BDA1A28E1164316BF818F67F014568D95D4FA968B0FE85DE209A0F41F45726C |
| Key | Value |
|---|---|
| MD5 | 5CDD60840BFC3AA403FD46EB061AF3DB |
| PackageArch | noarch |
| PackageDescription | Hashes are great for storing named data, but if you want more than one entry for a name, you have to use a list of pairs. Even then, this is really boring to write: $values = [ foo => undef, bar => undef, baz => undef, xyz => { ... }, ]; Just look at all those undefs! Don't worry, we can get rid of those: $values = [ map { $_ => undef } qw(foo bar baz), xyz => { ... }, ]; Aaaauuugh! We've saved a little typing, but now it requires thought to read, and thinking is even worse than typing... and it's got a bug! It looked right, didn't it? Well, the 'xyz => { ... }' gets consumed by the map, and we don't get the data we wanted. With Data::OptList, you can do this instead: $values = Data::OptList::mkopt([ qw(foo bar baz), xyz => { ... }, ]); This works by assuming that any defined scalar is a name and any reference following a name is its value. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | perl-Data-OptList |
| PackageRelease | lp151.2.1 |
| PackageVersion | 0.110 |
| SHA-1 | A55FA315299F34E14ECCA4B35B21C2CCA71C0F72 |
| SHA-256 | C943B3BFE5A87E92D393C490F2FF6639C257D6CFF6FD72ABEC31218FE3815A9A |
| Key | Value |
|---|---|
| MD5 | 711F21034DB45ED910E73AB93FBD982F |
| PackageArch | noarch |
| PackageDescription | Hashes are great for storing named data, but if you want more than one entry for a name, you have to use a list of pairs. Even then, this is really boring to write: $values = [ foo => undef, bar => undef, baz => undef, xyz => { ... }, ]; Just look at all those undefs! Don't worry, we can get rid of those: $values = [ map { $_ => undef } qw(foo bar baz), xyz => { ... }, ]; Aaaauuugh! We've saved a little typing, but now it requires thought to read, and thinking is even worse than typing... and it's got a bug! It looked right, didn't it? Well, the 'xyz => { ... }' gets consumed by the map, and we don't get the data we wanted. With Data::OptList, you can do this instead: $values = Data::OptList::mkopt([ qw(foo bar baz), xyz => { ... }, ]); This works by assuming that any defined scalar is a name and any reference following a name is its value. |
| PackageName | perl-Data-OptList |
| PackageRelease | bp152.2.1 |
| PackageVersion | 0.110 |
| SHA-1 | C692A151BD3C76DCA46CBF80F5A5EC5BDCFF0E66 |
| SHA-256 | 70B873667D406DC4CA8B3B12FB6FCCE57C81C37F1249600DF293295987745C48 |
| Key | Value |
|---|---|
| MD5 | 9418E38812D4BD782FC761C54AF2C49A |
| PackageArch | noarch |
| PackageDescription | Hashes are great for storing named data, but if you want more than one entry for a name, you have to use a list of pairs. Even then, this is really boring to write: $values = [ foo => undef, bar => undef, baz => undef, xyz => { ... }, ]; Just look at all those undefs! Don't worry, we can get rid of those: $values = [ map { $_ => undef } qw(foo bar baz), xyz => { ... }, ]; Aaaauuugh! We've saved a little typing, but now it requires thought to read, and thinking is even worse than typing... and it's got a bug! It looked right, didn't it? Well, the 'xyz => { ... }' gets consumed by the map, and we don't get the data we wanted. With Data::OptList, you can do this instead: $values = Data::OptList::mkopt([ qw(foo bar baz), xyz => { ... }, ]); This works by assuming that any defined scalar is a name and any reference following a name is its value. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | perl-Data-OptList |
| PackageRelease | lp152.3.2 |
| PackageVersion | 0.110 |
| SHA-1 | ABD5B01D46B92280F619BB9BA88E71616600D98E |
| SHA-256 | 719817AA3F2DD59F8C6054863ED5B9505B32FB24EAA3FEEE6BD09CA4F3742156 |
| Key | Value |
|---|---|
| MD5 | BB8E05B1560A1A0FFBBBD976DC25FD4F |
| PackageArch | noarch |
| PackageDescription | Hashes are great for storing named data, but if you want more than one entry for a name, you have to use a list of pairs. Even then, this is really boring to write: $values = [ foo => undef, bar => undef, baz => undef, xyz => { ... }, ]; Just look at all those undefs! Don't worry, we can get rid of those: $values = [ map { $_ => undef } qw(foo bar baz), xyz => { ... }, ]; Aaaauuugh! We've saved a little typing, but now it requires thought to read, and thinking is even worse than typing... and it's got a bug! It looked right, didn't it? Well, the 'xyz => { ... }' gets consumed by the map, and we don't get the data we wanted. With Data::OptList, you can do this instead: $values = Data::OptList::mkopt([ qw(foo bar baz), xyz => { ... }, ]); This works by assuming that any defined scalar is a name and any reference following a name is its value. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | perl-Data-OptList |
| PackageRelease | bp153.1.32 |
| PackageVersion | 0.110 |
| SHA-1 | 8D3E2929641063DD17EE47043E8C4C9F20EAAA25 |
| SHA-256 | 4CEAA012AD84B6F181DF8DA313F1EB5BC1D46BBC434AB41DA4598E60A927D05B |