use strict;
use warnings;
-our $VERSION = '1.09';
+use Class::MOP::Method::Meta;
+
+our $VERSION = '1.11';
$VERSION = eval $VERSION;
our $AUTHORITY = 'cpan:STEVAN';
sub method_metaclass { $_[0]->{'method_metaclass'} }
sub wrapped_method_metaclass { $_[0]->{'wrapped_method_metaclass'} }
+sub _meta_method_class { 'Class::MOP::Method::Meta' }
+
+sub _add_meta_method {
+ my $self = shift;
+ my ($name) = @_;
+ my $existing_method = $self->can('find_method_by_name')
+ ? $self->find_method_by_name($name)
+ : $self->get_method($name);
+ return if $existing_method
+ && $existing_method->isa($self->_meta_method_class);
+ $self->add_method(
+ $name => $self->_meta_method_class->wrap(
+ name => $name,
+ package_name => $self->name,
+ associated_metaclass => $self,
+ )
+ );
+}
# This doesn't always get initialized in a constructor because there is a
# weird object construction path for subclasses of Class::MOP::Class. At one
my ($old_meta) = @_;
for my $method ($old_meta->_get_local_methods) {
- # XXX: this is pretty gross. the issue here is that
- # CMOP::Method::Wrapped objects are subclasses of CMOP::Method, but
- # when we get to moose, they'll need to be compatible with
- # Moose::Meta::Method, which isn't possible. the right solution here is
- # to make ::Wrapped into a role that gets applied to whatever the
- # method_metaclass happens to be and get rid of
- # wrapped_method_metaclass entirely, but that's not going to happen
- # until we ditch cmop and get roles into the bootstrapping, so.
- # i'm not maintaining the previous behavior of turning them into
- # instances of the new method_metaclass because that's equally broken,
- # and at least this way any issues will at least be detectable and
- # potentially fixable. -doy
- if (!$method->isa($self->wrapped_method_metaclass)) {
- $method->_make_compatible_with($self->method_metaclass);
- }
+ $method->_make_compatible_with($self->method_metaclass);
$self->add_method($method->name => $method);
}
}