our TYPE EXPR : ATTRSour
associates a simple name with a package variable in the currentpackage for use within the current scope. When use strict 'vars'
is ineffect, our
lets you use declared global variables without qualifyingthem with package names, within the lexical scope of the our
declaration.In this way our
differs from use vars
, which is package-scoped.
Unlike my
or state
, which allocates storage for a variable andassociates a simple name with that storage for use within the currentscope, our
associates a simple name with a package (read: global)variable in the current package, for use within the current lexical scope.In other words, our
has the same scoping rules as my
or state
, butdoes not necessarily create a variable.
If more than one value is listed, the list must be placedin parentheses.
- our $foo;
- our($bar, $baz);
An our
declaration declares a global variable that will be visibleacross its entire lexical scope, even across package boundaries. Thepackage in which the variable is entered is determined at the pointof the declaration, not at the point of use. This means the followingbehavior holds:
- package Foo;
- our $bar; # declares $Foo::bar for rest of lexical scope
- $bar = 20;
- package Bar;
- print $bar; # prints 20, as it refers to $Foo::bar
Multiple our
declarations with the same name in the same lexicalscope are allowed if they are in different packages. If they happento be in the same package, Perl will emit warnings if you have askedfor them, just like multiple my
declarations. Unlike a secondmy
declaration, which will bind the name to a fresh variable, asecond our
declaration in the same package, in the same scope, ismerely redundant.
- use warnings;
- package Foo;
- our $bar; # declares $Foo::bar for rest of lexical scope
- $bar = 20;
- package Bar;
- our $bar = 30; # declares $Bar::bar for rest of lexical scope
- print $bar; # prints 30
- our $bar; # emits warning but has no other effect
- print $bar; # still prints 30
An our
declaration may also have a list of attributes associatedwith it.
The exact semantics and interface of TYPE and ATTRS are stillevolving. TYPE is currently bound to the use of the fields
pragma,and attributes are handled using the attributes
pragma, or, startingfrom Perl 5.8.0, also via the Attribute::Handlers
module. SeePrivate Variables via my() in perlsub for details, and fields,attributes, and Attribute::Handlers.