in reply to Re: odd things with my and our
in thread odd things with my and our

You've got a better understanding than jcpunk, but you don't have it quite right. "our" has the same scoping rules as "my" (perldoc -f our).

Replies are listed 'Best First'.
Re: Re: Re: odd things with my and our
by revdiablo (Prior) on Jan 25, 2004 at 09:48 UTC

    our has the same scoping rules as my, but only for the name of the variable. With our, the aliased name of the variable goes away at the end of the lexical scope, but the variable itself is still there. It is still accessible from its fully-qualified name, or with another our declaration.

    Here's a quick demonstration. This fails because the name $foo has gone out of lexical scope:

    $ perl -Mstrict -le '{ our $foo = "foo"; print $foo; } print $foo' Variable "$foo" is not imported at -e line 1. Global symbol "$foo" requires explicit package name at -e line 1. Execution of -e aborted due to compilation errors.

    But this succeeds because the variable itself is still around:

    $ perl -Mstrict -le '{ our $foo = "foo"; print $foo; } print $main::fo +o' foo foo

    That said, I'm not so sure what hardburn has not got "quite right." I don't really see him mention the name scoping of either types of variables anywhere in his post.