First, I thought of something like this:

But I thought, that it doesn't look nice ;) so I changed it to:

But both threw warnings that Log::Dispatch::warn is "used only once: possible typo..."; And then, based upon the answers from morgon and mr_mischief I thought of

sub Log::Dispatch::warn {
  my $self = shift;
  $self->warning(@_);
}
[download]

tested with:

#!/usr/bin/perl -l
use strict;
use warnings;

package foo;

sub new {
    bless {}, shift();
}

sub foo {
    my $self = shift;
    print "hello @_";
}

package main;

sub foo::bar {
    my ( $self ) = shift;
    $self->foo(@_);
}

*foo::baz  = \&foo::foo;
*foo::buzz = *foo::foo;

my $o = foo->new();

$o->bar('world');
$o->baz('world');
$o->buzz('world');

__END__
[download]

But both threw warnings that Log::Dispatch::warn is "used only once: possible typo...";

And both are the Right Way to alias a function. Warnings are hints, not laws.

And both are the Right Way to alias a function. Warnings are hints, not laws.

I didn't write, that it's a wrong way. And I didn't write about warnings being laws. I like to get rid of warnings without writing no warnings;, so I mentioned another way which doesn't show a warning.

Is it bad to look for ways to avoid warnings without writing no warnings;?

sub foo::bar {
  my ( $self ) = shift;
  $self->foo(@_);
}
[download]

So, is that so much worse than aliasing the function?

All in all, I I don't know how to handle your answer.
What's your intention?
Just information, that the aliasing was done right?
Should I consider something else?

Thanks in advance for your explanation.