Don't go mucking around with special global vars w/o localizing them first (at least, not when giving advice to others)! Even if it doesn't make much of a difference in this small script, it is a bad habit to get into and *will* come back to bite in a longer program. 
#!/bin/perl -w
use strict;
{
   local $/="|--------------------------------------|\n";
    while( <DATA>) {
      [SNIP]
   }
   [SNIP]
}

### Here in the program, the <FH> operator will now behave normally
### Before you could have been burned, since any other calls 
### to <FH> would see the specialized value of $/, even calls
### in subroutines.  As you can imagine, this is a pain to debug
### Its best to avoid this trap altogether as I have done above.

[download]
Update: Added parenthetical clarification....

-Blake

In reply to Re: Re: processing text from flat file by blakem
in thread processing text from flat file by Anonymous Monk

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.