You will need to rewrite your data file to get records separated by newlines. As an alternative, you can redefine perl's idea of an input record.

You can set the input record separator, $/ to your file's delimiter, here ';'. local should be used since $/ is a global.

{ local $/ = ';'; # input record separator - this is what chomp eats local $\ = "\n"; open(FILE, $adfile) || die "Can't open $adfile", $!; open(NEWFILE, "> $adfile.new") || die "Can't open new $adfile", $! +; while (<FILE>) { chomp; print NEWFILE; } close(NEWFILE>; close(FILE); }

The example here writes you a new data file with newlines.

After Compline,
Zaxo

Update: repaired loss of last record if ';' not present


In reply to Re: telling script to read from next line by Zaxo
in thread telling script to read from next line by ginocapelli

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.