Parents (Total: 22)

The searched file hash is included in 22 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	54908993446E08B65CB0DE9BA91A653A
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. This package overrides the isa() method, allowing your class to claim it's a class it's not (that is, isn't in @ISA).
PackageMaintainer	Fedora Project
PackageName	perl-asa
PackageRelease	1.el8
PackageVersion	1.04
SHA-1	04956013CB8225F29D1CFABFFB65C035425B1472
SHA-256	3C79E94DE3F53AF32D5045BA3DC02283A9A72C9F6F5F184747F1B623DC70076F

Key	Value
MD5	04ECAA8A2834C9B120C6BA11471F018A
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	lp150.7.1
PackageVersion	1.04
SHA-1	1DE86B16BDBCE82B218161922504A7F45444DAAB
SHA-256	1538982186D5A176189AD543597A6F5D9E25408084ED126B36B1EFA3FC0A2E29

Key	Value
MD5	EE9F7A0059E60D84AF8B28E790AD6390
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing".
PackageMaintainer	umeabot <umeabot>
PackageName	perl-asa
PackageRelease	2.mga9
PackageVersion	1.40.0
SHA-1	26C135BE48C519BDD7CFC60E522AA1CB22F2E9CC
SHA-256	70E5C8651E9C11066BA9BBC583589C3D70E1BB6F4FB570E7A96A3461AB6346C9

Key	Value
MD5	27E264F6535B27EEAD4BECFDE9F01282
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	lp151.7.1
PackageVersion	1.04
SHA-1	39C74968333E19F0736CE336C71AF1181C1C97AD
SHA-256	E5F1A54AFA92748308541915A91866E142671D6CFFB299677F1872A7DBF8A9B5

Key	Value
MD5	2EF33E2D40BF233F1BDCFC745ED8DBE3
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	1.24
PackageVersion	1.04
SHA-1	4557E2946676A13C6FA83071E9017EBB366C7FC7
SHA-256	E17DEFB58485BAA2E9F68D3A858722D8A4DAF6EBDB14512455D04F159D7420AA

Key	Value
MD5	D06D9DD3063C2AEE0C3584A9985CE86E
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	7.3
PackageVersion	1.04
SHA-1	4979C9579959EA6E70872284FCEE10CCFAA87BFA
SHA-256	7427714D4A158EEC3CC1BC57F24BF547313580C709C4542FED7125E207E1FD6D

Key	Value
MD5	9B5E764BB4020807E3559E85554DABE6
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. This package overrides the isa() method, allowing your class to claim it's a class it's not (that is, isn't in @ISA).
PackageMaintainer	Fedora Project
PackageName	perl-asa
PackageRelease	4.fc33
PackageVersion	1.04
SHA-1	4BCF3B0F858C6CDE5304BC89E9FF9919036CD40A
SHA-256	C63D65EE5F684D77B67CECB465012C918174EB36977EA21924361AF2CCDE3B18

Key	Value
MD5	CF2705EDE9D2BB6562173563CD848AC7
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	7.1
PackageVersion	1.04
SHA-1	58866CBF873D8B96E9EF4BD02B6FE73F45F918C7
SHA-256	1EDB9933FE2E0F4F3BF1C154A08C1F0020F90815685042435B66FF081A5E03B5

Key	Value
MD5	9D921A635C95F3AACD6781B9F3D2D1AD
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. This package overrides the isa() method, allowing your class to claim it's a class it's not (that is, isn't in @ISA).
PackageMaintainer	Fedora Project
PackageName	perl-asa
PackageRelease	2.fc32
PackageVersion	1.04
SHA-1	65BF2C45EE6296CF44C2654998081EFD3D6FAB99
SHA-256	F4F4F2D1708E6BE31E8A4EED384066D1BF36974E32C8864CDDE40FB8B6635562

Key	Value
MD5	2686D6E88E0433A87FDD708E42558E4C
PackageArch	noarch
PackageDescription	Perl 5 doesn't natively support Java-style interfaces, and it doesn't support Perl 6 style roles either. You can get both of these things in half a dozen different ways via various CPAN modules, but they usually require that you buy into "their way" of implementing your code. Other have turned to "duck typing". This is, for the most part, a fairly naive check that says "can you do this method", under the "if it looks like a duck, and quacks like a duck, then it must be a duck". It assumes that if you have a '->quack' method, then they will treat you as a duck, because doing things like adding 'Duck' to your '@ISA' array means you are also forced to take their implementation. There is, of course, a better way. For better or worse, Perl's '->isa' functionality to determine if something is or is not a particular class/object is defined as a *method*, not a function, and so that means that as well as adding something to you '@ISA' array, so that Perl's 'UNIVERSAL::isa' method can work with it, you are also allowed to simply overload your own 'isa' method and answer directly whether or not you are something. The simplest form of the idiom looks like this. sub isa { return 1 if $_[1] eq 'Duck'; shift->SUPER::isa(@_); } This reads "Check my type as normal, but if anyone wants to know if I'm a duck, then tell them yes". Now, there are a few people that have argued that this is "lying" about your class, but this argument is based on the idea that '@ISA' is somehow more "real" than using the method directly. It also assumes that what you advertise you implement needs to be in sync with the method resolution for any given function. But in the best and cleanest implementation of code, the API is orthogonal (although most often related) to the implementation. And although '@ISA' is about implementation *and* API, overloading 'isa' to let you change your API is not at all bad when seen in this light.
PackageName	perl-asa
PackageRelease	7.1
PackageVersion	1.04
SHA-1	674639FEF1B8D43E60B52C9DDF8B2E616445F02E
SHA-256	DF9660E48A2AD2D71D0EB5F54404F8A052B4B6AA14C939B6CE18220998B3FF19