A friend was bemoaning a few Linux quota tools that gave hard-to-parse output. It would output a header line, followed by a number of lines of data. An example:
Filesystem blocks quota limit grace files ... /dev/hdd3 26320 46080 51200 1521 ... /dev/hdd4 26320 51200 1060 ...
My friend's problem was trying to deal with the "empty" columns in the data lines. When just using a naive split(), the empty columns would disappear, throwing off the count.
# controlled search-and-replace to insert column markers # using the header line as a guide to where the columns lie $headers = <>; $headers =~ s/(\S)\s/$1\#/g; while (<>) { s/\s/ (substr($headers, pos(), 1) eq '#')? '#' : ' ' /eg; @_ = split /\s*\#\s*/; # @_ now has true columns ready for whitespace trimming }

In reply to parsing sloppy text from columns by halley

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.