I jsut had the same problem... 

[root@gw /]# uname -a
Linux gw 2.4.22 #8 SMP Wed Sep 24 13:53:53 EDT 2003 i686 i686 i386 GNU
+/Linux
[root@gw /]# perl -v

This is perl, v5.8.0 built for i386-linux-thread-multi

Copyright 1987-2002, Larry Wall

[root@gw /]# cat test
#!/usr/bin/perl

$file = "/proc/net/snmp";
$ABC = 0;

while ( $i ne 0 ) {
  &GET;
  $RATE = $FIELDS[3] - $ABC;
  $ABC = "$FIELDS[3]";
  print "$RATE\n";
}

sub GET {
  open (FILE, $file);
  @LINES = <FILE>;
  close (FILE);
  $LINE = $LINES[1];
  @FIELDS = split(/ /, $LINE);
  sleep 1;
}

[download]

*NOTE - I had to remove the \s. look like perl 5.8.0 thats shipping with redhat 8.0 does not like splitting on a space using the \s RE

janitored by ybiC: add balanced <code> tags around code block, as per Monastery convention

In reply to Re: Split loop error with perl 5.8 by Anonymous Monk
in thread Split loop error with perl 5.8 by Lars Povlsen

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.