I'm going to stick up for Red Hat here - I just installed 8.0, and during my config, I couldn't help but read PM. Probably dangerous as root, but hey. Here's a copy and paste, using grinder's example. 
[root@localhost root]# cat split.pl
#! /usr/bin/perl -w

use strict;

my $x1 = 'aaa bbb cc';
my $x2 = 'aa, bb, cc';

print join( '-', split(/[\s,]+/, $x1)), "\n";
print join( '-', split(/[\s,]+/, $x2)), "\n";
[root@localhost root]# ./split.pl
aaa-bbb-cc
aa-bb-cc
[root@localhost root]# perl -v

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

[download]
Seems to have worked just fine for me, so now I think it's a context thing, something about how you're using it. :) I'm using the Perl available via RPM, I haven't downloaded a snippet of source yet except for grinder's code. hehe.

~Brian

In reply to Re: Split loop error with perl 5.8 by brianarn
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.