in reply to Re: the "our" declaration ?!!
in thread the "our" declaration ?!!

It's kinda like no strict 'vars';, but it only applies to a single variable.

It means "yes, a package variable with that name exists, so don't complain about it."

Thats a common but incomplete interpretation. "our" works also useful without "strict", so it's not about complaining or not.

And there are important differences to no strict 'vars', because the chosen namespace can be very different from what you expect: With our it's the stash of the package at declaration position, like with my where it's the lexpad at declaration position.

But with no strict 'vars' a "non-explicit" variable belongs to the actual package at the encounter position!

Cheers Rolf

UPDATE: So one can't simply refactor a code be replacing no strict 'vars' with a lot of ours for each variablename. You have to take care about the local packages!

Replies are listed 'Best First'.
Re^3: the "our" declaration ?!!
by ikegami (Patriarch) on Jan 20, 2009 at 18:49 UTC

    Thats a common but incomplete interpretation.

    Correct, but only if you allow for poorly scoped variables. As I see things, my explanation is complete except in buggy programs. Put curlies around your packages when you have more than one in your file.

[reply]
      don't know what you mean, the following code is with curlies but produces different output for the two options. 
      use strict;

no strict "vars";  # option1
#our $x;        # option2

$x="main";

{
    package other;
    $x="other";
    print $x;
}

print $x;

__END__
1: othermain
2: otherother

      [download]

      Cheers Rolf

[reply]
[d/l]
        ...and don't nest your packages. I thought that went without saying.

        If you do nest your packages to share private variables, you should be using my, not our.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom