What happens when you want to use the real pos()? I'm not worried about the methods. I'm talking about using the builtins, which you don't call as methods. :)

Update: You have to be able to explain to everyone else who looks at your code why Perl ignores the subroutine you defined, which one you really wanted, and all sorts of other things. pos() may not be the best example though.

#!/usr/bin/perl
use warnings;

sub shift { }

my @array = qw( 1 2 3 );

shift @array;
[download]

In general, don't purposedly cause ambiguity.

What happens when you want to use the real pos()? I'm not worried about the methods. I'm talking about using the builtins, which you don't call as methods. :)

?

use strict;
use warnings;

{   package Foo;
    
    sub pos { "pos" }
    
    sub bar {
        my $foo = "xxx";
        $foo =~ m/x/g;
        return pos $foo;
    };
    
};

use Test::More 'no_plan';
is( Foo->pos, "pos",    "we can call Foo's pos method"  );
is( Foo->bar, 1,        "and still use pos inside the package" );
[download]

That’s exactly the point: there’s a call to pos, but it invokes pos, not your sub pos. That call to pos is ambiguous to the reader.

I agree with brian on this one.

Makeshifts last the longest.