So, is there a reason (technically, best practice, etc) that I should not just use this format:

How big is your monitor? :)

FWIW, a best practice policy might outlaw $$fa{$fa}{$fb}{$fc}{$fa}{$fq}{$fp} or even $fa->{$fa}{$fb}{$fc}{$fa}{$fq}{$fp} and demand intermediates or even helpers 

{
    use Data::Diver qw/ Dive /;
    my $metric = Dive( $mainHash , $hashType , $regionID, 'MetricType'
+ );
    my $cirtem = Dive( $metric, $$resultHash{Location} , $yearMonthDat
+eList[$start] );
    $cirtem +=  $$resultHash{Value};
}

[download]

If you make $mainHash an object it might collapse into 

{
   $mash->mertem( $mash->mertem + $value );
}

[download]

In reply to Re: $var{el} += 1 vs $var{el} = $var{el} + 1 by Anonymous Monk
in thread $var{el} += 1 vs $var{el} = $var{el} + 1 by banesong

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.