Not exactly. By using my, you declare new hashes. If you used warnings, Perl would tell you:
"my" variable %hash1 masks earlier declaration in same scope

So, the statement is equivalent to

my (%hash1, %hash2, %hash3);

Note that the hash %_ is not cleared, because the body of the loop is not run (the brand new hashes are emtpy).

Without my, %_ would be cleared, but %hash1 and company would stay untouched. To test, just play with comments in the following code:

# use strict; use warnings; %_ = (u => 2); %hash1 = (b => 3); # %hash1 = (b => 3); # %_ = () for my (%hash1,%hash2,%hash3); # %_ = () for (%hash1,%hash2,%hash3); print %_, %hash1, "\n";

To clear a hash, use undef or %hash = ().

لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

In reply to Re: Clear / Initialize multiple hashes by choroba
in thread Clear / Initialize multiple hashes by acadey

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.