Variables declared with our create a package variable and a lexically scoped variable
That suggests any use of our creates two variables. It doesn't. It creates an alias (another name) for the variable - the alias is lexically scoped. And no matter how many times you use our, it doesn't create new variables over and over again - unlike my. 
my $foo++;  say $foo;
my $foo++;  say $foo;
our $bar++; say $bar;
our $bar++; say $bar;
__END__
1
1
1
2

[download]
It does warn. But even if you put all the lines in different scopes (no warnings then), it's still the same variable when using our: 
{my $foo++;  say $foo;}
{my $foo++;  say $foo;}
{our $bar++; say $bar;}
{our $bar++; say $bar;}
__END__
1
1
1
2

[download]

In reply to Re^4: Best practices - if any? (our) by JavaFan
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.