You know it’s perfectly acceptable to edit code as long as it’s marked as updated. You should correct it to run and mark it as such. It’s nice to see you post some code. I have to say though that if you can’t even write a correct comment in Perl, let alone code that will compile—and can’t be bothered to fix it—it’s really time to back up for some introspection about your participation here and what you hope to achieve going forward.

You’ve always been polite, friendly, and encouraging here and that carries some weight but you’re not really offering anything else and you’re sabotaging yourself and your technical reputation. Take a break? Change gears from seasoned expert to cautious learner? Something has to give.

In reply to Re^4: Parsing line by line by Your Mother
in thread Parsing line by line by AWallBuilder

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.