... best practice [to] put your code in < code > < /code > tags ...

gingeremmie:
... and also data, input and output. For example, if the data of the OP had been in code tags, it would not be necessary to tediously edit (and possibly corrupt) the data in order to provide an example solution, and that might make it more likely that some busy monk will take the time to provide the example. Please see Writeup Formatting Tips, Markup in the Monastery and How do I post a question effectively?.
(BTW: Because you posted originally as a registered monk, you can go back and update your OP to include the code tags! Hint, hint...)

In reply to Re^2: Parsing multiple rows of text and converting to columns by AnomalousMonk
in thread Parsing multiple rows of text and converting to columns by gingeremmie

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.