in reply to Re: print() on closed filehandle..
in thread print() on closed filehandle..

Ah.. so 'our' is like 'global' in other languages? (opposite of 'my')? 
 ___
/\__\ "What is the world coming to?"
\/__/ www.wolispace.com

[download]

Replies are listed 'Best First'.
Re: Re: Re: print() on closed filehandle..
by ysth (Canon) on Feb 05, 2004 at 05:50 UTC
    Not exactly. global variables just spring into existence when the compiler notices them, so our() doesn't really declare them, per se. our() serves a few different purposes. One is to get rid of the "used only once" warning (which is intended to help catch typos in variable names). If you run with use strict "vars"; turned on, you'll usually have to use our() on user variables native to a package but not qualified by a package (aka namespace). This is also intended to help catch typos in variable names.

    our() also will hide a my() variable for a certain scope: 

    perl -we '$x = "global"; my $x = "local"; our $x; print $x'
global

    [download]
    Here there are two different $x variables; the global $x that lives in the symbol table for the main:: package, and a lexical $x that lives in a pad (a kind of temporary storage attached to each subroutine or source file (though one pad can have multiple variables of the same name with different scopes within the subroutine)). Normally in the scope of a my($var), $var will refer to the lexical variable. our($var) can be used to override that to the end of the enclosing block.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom