1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
NAME
asa - Lets your class/object say it works like something else
SYNOPSIS
#########################################
# Your Code
package My::WereDuck;
use base 'My::Lycanthrope';
use asa 'Duck';
sub quack {
return "Hi! errr... Quack!";
}
################################################
# Their Code
sub strangle {
my $duck = shift;
unless ( $duck->isa('Duck') ) {
die "We only strangle ducks";
}
print "Farmer Joe wrings the duck's neck\n";
print "Said the duck, '" . $duck->quack . "'\n";
print "We ate well that night.\n";
}
DESCRIPTION
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.
What does asa.pm do?
Much as base provides convenient syntactic sugar for loading your parent
class and setting @ISA, this pragma will provide convenient syntactic
sugar for creating your own custom overloaded isa functions.
Beyond just the idiom above, it implements various workarounds for some
edge cases, so you don't have to, and allows clear seperation of
concerns.
You should just be able to use it, and if something ever goes wrong,
then it's my fault, and I'll fix it.
What doesn't asa.pm do?
In Perl, highly robust introspection is really hard. Which is why most
modules that provide some level of interface functionality require you
to explicitly define them in multiple classes, and start to tread on
your toes.
This class does not do any strict enforcement of interfaces. 90% of the
time, what you want to do, and the methods you need to implement, are
going to be pretty obvious, so it's your fault if you don't provide
them.
But at least this way, you can implement them however you like, and
"asa" will just take care of the details of safely telling everyone else
you are a duck :)
What if a Duck method clashes with a My::Package method?
Unlike Perl 6, which implements a concept called "multi-methods", Perl 5
does not have a native approach to solving the problem of "API
collision".
Originally from the Java/C++ world, the problem of overcoming language
API limitations can be done through the use of one of several "design
patterns".
For you, the victim of API collision, you might be interested in the
"Adapter" pattern.
For more information on implementing the Adapter pattern in Perl, see
Class::Adapter, which provides a veritable toolkit for creating an
implementation of the Adapter pattern which can solve your problem.
SUPPORT
Bugs should be always be reported via the CPAN bug tracker at
<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=asa>
For other issues, or commercial enhancement or support, contact the
author.
AUTHORS
Adam Kennedy <adamk@cpan.org>
SEE ALSO
<http://ali.as/>
COPYRIGHT
Copyright 2006 - 2011 Adam Kennedy.
This program is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included
with this module.
|
