Re: method aliases with goto(&NAME)

Won't somebody please think of the children?!?!.

package Parent {
   sub legacy_method {
      my ($self, @args) = @_;
      return $self->current_method(@args);
   }
   sub current_method {
      return 1;
   }
}

package Child {
   use base 'Parent';
   sub current_method {
      return 2;
   }
}

Child->legacy_method;  # returns 2
[download]

If you swap in your goto implementation of the legacy method, then calling Child->legacy_method returns 1.

Here's an alternative safer version using goto...

sub legacy_method {
  my $next = $_[0]->can('current_method');
  goto $next;
}
[download]

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Comment on Re: method aliases with goto(&NAME) Select or Download Code

Replies are listed 'Best First'.
Re^2: method aliases with goto(&NAME) by LanX (Saint) on Sep 18, 2013 at 13:01 UTC
> If you swap in your goto implementation of the legacy method, then calling Child->legacy_method returns 1. Don't you think this could perfectly be the intended behavior, since Child doesn't seem to have any `legacy_method`? But your right that the OP was wrong about the equivalence. Cheers Rolf ( addicted to the Perl Programming Language)	[reply] [d/l]
Re^3: method aliases with goto(&NAME) by tobyink (Canon) on Sep 18, 2013 at 13:26 UTC
There are probably instances where you'd want two methods that behave identically in the parent class, but behave differently in the child class. However, given that the title of this thread mentioned "method aliases", I'm assuming the intention is that `legacy_method` acts as an alias (i.e. behaves identically) for `current_method`, unless a child class explicitly overrides `legacy_method` to make it behave differently. `use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name`	[reply] [d/l] [select]
Re^4: method aliases with goto(&NAME) by LanX (Saint) on Sep 18, 2013 at 14:53 UTC
I had the impression that `legacy_method` is supposed to be deprecated and that overloading in new children is maybe not intended. Well I don't like speculating about the OPs intention, let's wait what he says... :) Cheers Rolf ( addicted to the Perl Programming Language)	[reply] [d/l]
Re^3: method aliases with goto(&NAME) by ikegami (Patriarch) on Sep 18, 2013 at 19:27 UTC
Don't you think this could perfectly be the intended behavior, since Child doesn't seem to have any legacy_method? Not for one second. The child provides a correct interface. The legacy caller uses a correct interface. It should work.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks