Re^2: This could have DWIM better

[demerphq]

in reply to Re: This could have DWIM better
in thread This could have DWIM better

I daren’t use it in any complex codebase that relies on a lot of CPAN code either.

Why? I thought that this trick would only affect the module its declared in. Its not going to have a global effect fwir.

[Aristotle]

Quoth perlsub:

Library modules should not in general export built-in names like open or chdir as part of their default @EXPORT list, because these may sneak into someone else’s namespace and change the semantics unexpectedly. Instead, if the module adds that name to @EXPORT_OK, then it’s possible for a user to import the name explicitly, but not implicitly. That is, they could say

use Module 'open';

and it would import the open override. But if they said

use Module;

they would get the default imports without overrides.

The foregoing mechanism for overriding built-in is restricted, quite deliberately, to the package that requests the import. There is a second method that is sometimes applicable when you wish to override a built-in everywhere, without regard to namespace boundaries. This is achieved by importing a sub into the special namespace CORE::GLOBAL::.

Emphasis mine.

[demerphq]

Ah, thanks for the clarification. I misremembered this. Am I correct that this doesnt apply to prototypeless routines like print?