Perhaps a little more clarification on what im doing is in order. (Of course this problem exists everywhere). I write a lot of data migration programs at work, and this problem usually arises when i get some nasty data and have to do all sorts of experimentation just to figure out what to do with the data...as that process goes along i continually modify what is being reported about the process itself. Most of the things being reported are merely counters, but i always end up keeping track of details for various anomolies. During development i find it easiest to just have a hash(ref) that is the main report accumulator, and i throw in whatever needs to be reported. This continually changes. Once the main development / research is complete, i have a good idea of what will ultimately get reported and i can lock down the report accumulator as a class or a hashref if it ends up simplistic.

One way to help me detect these errors would be to do a Dumper on the report hashref, in addition to the lightly formatted reporting that is going on during development.

I am quite anal about good programming techniques, this is just one that sometimes gets the best of me. These reporters are what i would consider on the edge of being quick and dirty / needing more formal structure - this probably means that they should probably get the more formal treatment.

Thanks for all the advice, looking forward to a weekend of studying

In reply to Re: avoiding hash key typos by shemp
in thread avoiding hash key typos by shemp

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.