$strict::VERSION
= "1.03";
push @wrong, $s unless exists $bitmask{$s};
$bits |= $bitmask{$s} || 0;
Carp
::croak
("Unknown 'strict' tag(s) '@wrong'");
my $default_bits = bits
(qw(refs subs vars));
$^H
|= @_ ? bits
(@_) : $default_bits;
$^H
&= ~ (@_ ? bits
(@_) : $default_bits);
strict - Perl pragma to restrict unsafe constructs
If no import list is supplied, all possible restrictions are assumed.
(This is the safest mode to operate in, but is sometimes too strict for
casual programming.) Currently, there are three possible things to be
strict about: "subs", "vars", and "refs".
This generates a runtime error if you
use symbolic references (see L<perlref>).
print $$ref; # runtime error; normally ok
print $file "Hi!"; # error; note: no comma after $file
There is one exception to this rule:
is allowed so that C<goto &$AUTOLOAD> would not break under stricture.
This generates a compile-time error if you access a variable that wasn't
declared via C<our> or C<use vars>,
localized via C<my()>, or wasn't fully qualified. Because this is to avoid
variable suicide problems and subtle dynamic scoping issues, a merely
local() variable isn't good enough. See L<perlfunc/my> and
$X::foo = 1; # ok, fully qualified
my $foo = 10; # ok, my() var
local $foo = 9; # blows up
our $bar; # Declares $bar in current package
$bar = 'HgS'; # ok, global declared via pragma
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.
This disables the poetry optimization, generating a compile-time error if
you try to use a bareword identifier that's 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 C<< => >> symbol.
$SIG{PIPE} = Plumber; # blows up
$SIG{PIPE} = "Plumber"; # just fine: quoted string is always ok
$SIG{PIPE} = \&Plumber; # preferred form
See L<perlmodlib/Pragmatic Modules>.
C<strict 'subs'>, with Perl 5.6.1, erroneously permitted to use an unquoted
compound identifier (e.g. C<Foo::Bar>) as a hash key (before C<< => >> 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) '...'