vars(3pm) [osx man page]

vars(3pm)						 Perl Programmers Reference Guide						 vars(3pm)

NAME

       vars - Perl pragma to predeclare global variable names (obsolete)

SYNOPSIS

	   use vars qw($frob @mung %seen);

DESCRIPTION

       NOTE: For variables in the current package, the functionality provided by this pragma has been superseded by "our" declarations, available
       in Perl v5.6.0 or later.  See "our" in perlfunc.

       This will predeclare all the variables whose names are in the list, allowing you to use them under "use strict", and disabling any typo
       warnings.

       Unlike pragmas that affect the $^H hints variable, the "use vars" and "use subs" declarations are not BLOCK-scoped.  They are thus
       effective for the entire file in which they appear.  You may not rescind such declarations with "no vars" or "no subs".

       Packages such as the AutoLoader and SelfLoader that delay loading of subroutines within packages can create problems with package lexicals
       defined using "my()". While the vars pragma cannot duplicate the effect of package lexicals (total transparency outside of the package), it
       can act as an acceptable substitute by pre-declaring global symbols, ensuring their availability to the later-loaded routines.

       See "Pragmatic Modules" in perlmodlib.

perl v5.16.2							    2012-10-25								 vars(3pm)

strict(3pm)						 Perl Programmers Reference Guide					       strict(3pm)

NAME

       strict - Perl pragma to restrict unsafe constructs

SYNOPSIS

	   use strict;

	   use strict "vars";
	   use strict "refs";
	   use strict "subs";

	   use strict;
	   no strict "vars";

DESCRIPTION

       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".

       "strict refs"
	     This generates a runtime error if you use symbolic references (see perlref).

		 use strict 'refs';
		 $ref = $foo;
		 print $$ref;	     # ok
		 $ref = "foo";
		 print $$ref;	     # runtime error; normally ok
		 $file = "STDOUT";
		 print $file "Hi!";  # error; note: no comma after $file

	     There is one exception to this rule:

		 $bar = &{'foo'};
		 &$bar;

	     is allowed so that "goto &$AUTOLOAD" would not break under stricture.

       "strict vars"
	     This generates a compile-time error if you access a variable that wasn't declared via "our" or "use vars", localized via "my()", or
	     wasn't fully qualified.  Because this is to avoid variable suicide problems and subtle dynamic scoping issues, a merely local() vari-
	     able isn't good enough.  See "my" in perlfunc and "local" in perlfunc.

		 use strict 'vars';
		 $X::foo = 1;	      # ok, fully qualified
		 my $foo = 10;	      # ok, my() var
		 local $foo = 9;      # blows up

		 package Cinna;
		 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.

       "strict subs"
	     This disables the poetry optimization, generating a compile-time error if you try to use a bareword identifier that's not a subrou-
	     tine, unless it appears in curly braces or on the left hand side of the "=>" symbol.

		 use strict 'subs';
		 $SIG{PIPE} = Plumber;	     # blows up
		 $SIG{PIPE} = "Plumber";     # just fine: bareword in curlies always ok
		 $SIG{PIPE} = &Plumber;     # preferred form

       See "Pragmatic Modules" in perlmodlib.

perl v5.8.0							    2002-06-01							       strict(3pm)