As rdfield already mentioned, your problem is in the assignment of open()'s result to your array @r.

When reading the file's content, remember that Perl doesn't remove the linebreaks automatically; that's up to you (use chomp() for that):

# ...
@r = <DATFH>;
chomp @r;

[download]
Instead of reading the complete file into an array (and into the memory) you can read linewise: 
#!/usr/bin/perl
use strict;
use warnings;

my $file = 'data.txt';

open my $datfh, '<', $file or die "$file: open(ro) failed: $!\n";

while ( my $line = <$datfh> ) {
  chomp $line;
  my @fields = split /\|/, $line;
  # work with your data fields
}

close $datfh or die "$file: close(ro) failed: $!\n";

[download]

update: paragraph tags and text added;
update2: typo fixed; thanks johngg

In reply to Re: array reading problem by linuxer
in thread array reading problem by jeah

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.