It would make using any non-strict module from a strict script impossible.

I'm not useing a module (.pm); I'm requireing a companion perl script (.pl). When one uses a module, naturally that module has its own autonomy with what it requires and uses.

Blessings,

~Polyglot~

> When one uses a module, naturally that module has its own autonomy with what it requires and uses.

No idea what you mean, a use is basically a require + import at compile-time

Like documented:

BEGIN { require Module; Module->import( LIST ); }

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

the global variables are all correctly shared among the files--so why wouldn't strict be shared, too?

Because strict, warnings, and many other pragmas have a lexical scope. If used at the very top of the file, their scope is limited to that file. do, require, and use create a new lexical scope for the files they execute. Only evaled code inherits the strict and other pragmas from the surrounding lexical scope.

> Only evaled code inherits the strict and other pragmas from the surrounding lexical scope.

and because of the lexical scoping he can also deactivate most pragmas like strict before eval to avoid that problem

{ 
    no strict;
    eval $CODE;
}
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}