Re: Perl keywords for declaring variables: my, our and local???

our is a lexically scoped alias for a global variable. Will create the global if it didn't exist already.

See the following code:

#!/usr/bin/perl

our $a = "foo";

print "$a\n";


package Our;

print "$Our::a  <--shouldn't print anything here\n";
print "$main::a <--should print 'a' from the main symbol table here\n"
+;
print "$a       <--should also print 'a' from the main symbol table he
+re\n\t\tdue to lexically scoped alias\n";
[download]

Results are:

foo
        <--shouldn't print anything here
foo     <--should print 'a' from the main symbol table here
foo     <--should also print 'a' from the main symbol table here
                due to lexically scoped alias
[download]

By default any global variables you create automatically populate the "main" symbol table, %main::. With a package declaration you could change which symbol table you are populating when you declare unqualified variables.

But our is a lexical decalaration. In the case above the declaration was file scoped. That's why I still got something back when I gave it an unqualified print statement print "$a\n" after the package declaration.

Don't forget just because it's a lexically scoped variable, it's still an alias for a global variable. Hence when I reassigned $a = "foo" with the our declaration, I blew away the old value.

Any comments are welcome.
Cheers,
Kristina

Comment on Re: Perl keywords for declaring variables: my, our and local??? Select or Download Code

Replies are listed 'Best First'.
Re: Re: Perl keywords for declaring variables: my, our and local??? by demerphq (Chancellor) on Mar 23, 2003 at 10:07 UTC
our is a lexically scoped alias for a global variable. Will create the global if it didn't exist already This is a little misleading. Global variables are created on first use regardless. And when you say alias I can see what you mean but wouldnt use that term personally. strict complains if it sees a symbol that isn't a fully qualified package variable (aka global) or if it hasn't been declared by my or it doesnt meet a handful of esoteric exceptions (like $_ and $a $b). our is the workaround to tell strict that in a given lexical scope a given symbol defaults to meaning the package variable and not to worry if it hasnt been declared already as a lexical. It means you don't have to fully qualify your globals, which also means that strict can catch your typos. An alternate means to accomplish this goal is to use vars qw(); which I personally prefer. By default any global variables you create automatically populate the "main" symbol table, %main::. With a package declaration you could change which symbol table you are populating when you declare unqualified variables. Again this is correct but IMO a little muddled. Unqualified globals (with certain exceptians left aside) are presumed to refer to the package in which they are used. If no package declaration is provided then it defaults to 'main'. To fully qualify something to main you need not write $main::foo but rather $::foo. But again declaration does not directly mean creation or population. It does indirectly as it potentially means "first use" but its the "first use" rule that creates the var and not the declaration. Ie: `package Foo; use strict; use vars qw/$DEBUG/; our $DEBUG; $Foo::DEBUG=1;` [download] neither "declaration" is necessary in this case at all. Personally I like to think of it this way: "our and use vars advise strict not to complain about unqualified globals.", "my declares a new lexical variable" and "local creates a new dynamic scope for a variable" --- demerphq	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: Perl keywords for declaring variables: my, our and local???
by demerphq (Chancellor) on Mar 23, 2003 at 10:07 UTC

our is a lexically scoped alias for a global variable. Will create the global if it didn't exist already

This is a little misleading. Global variables are created on first use regardless. And when you say alias I can see what you mean but wouldnt use that term personally. strict complains if it sees a symbol that isn't a fully qualified package variable (aka global) or if it hasn't been declared by my or it doesnt meet a handful of esoteric exceptions (like $_ and $a $b). our is the workaround to tell strict that in a given lexical scope a given symbol defaults to meaning the package variable and not to worry if it hasnt been declared already as a lexical. It means you don't have to fully qualify your globals, which also means that strict can catch your typos. An alternate means to accomplish this goal is to use vars qw(); which I personally prefer.

By default any global variables you create automatically populate the "main" symbol table, %main::. With a package declaration you could change which symbol table you are populating when you declare unqualified variables.

Again this is correct but IMO a little muddled. Unqualified globals (with certain exceptians left aside) are presumed to refer to the package in which they are used. If no package declaration is provided then it defaults to 'main'. To fully qualify something to main you need not write $main::foo but rather $::foo. But again declaration does not directly mean creation or population. It does indirectly as it potentially means "first use" but its the "first use" rule that creates the var and not the declaration. Ie:

package Foo;
use strict;

use vars qw/$DEBUG/;

our $DEBUG;

$Foo::DEBUG=1;
[download]

neither "declaration" is necessary in this case at all.

Personally I like to think of it this way: "our and use vars advise strict not to complain about unqualified globals.", "my declares a new lexical variable" and "local creates a new dynamic scope for a variable"

[reply]
[d/l]
[select]