This generates a runtime error if you
use symbolic references (see perlref).
There is one exception to this rule:
is allowed so that goto &$AUTOLOAD would not break under stricture.
This generates a compile-time error if you access a variable that was
neither explicitly declared (using any of my, our, state, or use
vars) nor fully qualified. (Because this is to avoid variable suicide
problems and subtle dynamic scoping issues, a merely local variable isnt
good enough.) See my in perlfunc, our in perlfunc, state in perlfunc,
local in perlfunc, and vars.
The local() generated a compile-time error because you just touched a global name without fully qualifying it.
Because of their special use by sort(), the variables $a and $b are exempted from this check.
|strict subs||This disables the poetry optimization, generating a compile-time error if you try to use a bareword identifier thats not a subroutine, unless it is a simple identifier (no colons) and that it appears in curly braces or on the left hand side of the => symbol.|
strict subs, with Perl 5.6.1, erroneously permitted to use an unquoted compound identifier (e.g. Foo::Bar) as a hash key (before => or inside curlies), but without forcing it always to a literal string.
Starting with Perl 5.8.1 strict is strict about its restrictions: if unknown restrictions are used, the strict pragma will abort with
Unknown strict tag(s) ...
As of version 1.04 (Perl 5.10), strict verifies that it is used as strict to avoid the dreaded Strict trap on case insensitive file systems.
|perl v5.22.1||STRICT (3)||2015-10-17|