Consider adding at least a paragraph or two on the "other" inverse of split - matching /(...)/g in a list context:

my @words = split /\s+/, $string;
my @words = $string =~ /(\S+)/g;
[download]

For these two, it's equally easy to say what you want to throw away vs what you want to keep. But sometimes, it's easier to say what you want to keep:

my @bignums = $string =~ /(\d{4,})/;g
[download]

That'd be hard to do as a split. And sometimes, it's easier to say what you want to throw away:

my @funny_delimited = split /(?:,\s+|###|!delim!)/, $string;
[download]

So, both of them are useful to know. Far too often, I see one being used where the other would be quite nice. Keep them both nearby in your toolbox.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.