Yes this is badly organised but you do not show any data processing. You have a series of lines of the format 

if ( $this ) { print "You have obtained $this this stuff\n"; }

[download]

How you got to this stage is not show, nor is a sample of the file format you are parsing. strict works fine and the errors you get will have a meaning. You need to post some sample log data your complete code if you really want answers. Use <readmore> tag to hide lengthy stuff like the data and code. Ask specific questions like "Why does strict complain about this?", "How can I parse this data efficiently?" or like you have said "This is ugly but I don't know enough perl to make it better. Suggestions welcome!"

In reply to Re: help with "use strict" and code organization by tachyon-II
in thread help with "use strict" and code organization by MrFloydFreak42

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.