But even if you put all the lines in different scopes (no warnings then), it's still the same variable when using our:

...as long as the alias refers to the same package variable. An our in an inner scope creates a new alias: 

our $foo;
{
  our $foo = 'foo'; say $foo;
}
{
  package Foo;
  our $foo = 'bar'; say $foo;
}
package main; say $foo;
package Foo; say $foo;
{
  package Foo;
  our $foo; say $foo;
  {
    package Bar;
    our $foo = 'quux'; say $foo;
  }
  say $foo;
}
{
  package Foo;
  say $foo;
}
__END__
foo
bar
foo
foo
bar
quux
bar
foo

[download]

In reply to Re^5: Best practices - if any? (our) by shmem
in thread Best practices - if any? by AriSoft

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.