What are you talking about?

I don't want to collide with any other product which is using My:: for its own purpose. Of course does the caller change.

But any magic should be restricted to the local scope!

Anyway reserving the Namespace on CPAN would be needed.

update

another idea would be using a lexical object, and the method call would be channeled through AUTOLOAD.

my $mysubs = new Mysubs;

$mysubs->xyz();
[download]

this could indeed work without polluting other packages and the runtime effects would become obvious by the ->arrow .

Ah, right. I understood that you were saying that calling My::function from a module that does not define function would yield unexpected results. The actual message makes more sense :D.

If there are already package that use My:: without having reserved the keyword, they already are risky on their own anyway, if you ever end up including more than one of those in one program.

my philosophy is that nobody else should try to use my personal footgun for his own limbs. ;-)

BTW: the object thing could work, but I won't implement it, cause this reeks strongly like an XY problem.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}