I just browsed several records and seemed to me that
quite a few people (and including me) like to see that
"split" based on argument type. If it is a string, then
use string as the separator. For Regexp, use the Regexp.
This is basically the Ruby way to overload “split” method.
Was there a final decision on this? A lot of codes could break
due to this change.
From POP3 Thu Aug 22 12:37:00 EDT 2002
Date: Fri, 23 Aug 2002 00:32:26 +0900
Posted: 22 Aug 2002 09:41:13 -0600
From: Tom Sawyer email@example.com
Subject: Re: split warning
To: firstname.lastname@example.org (ruby-talk ML)
X-MLServer: fml [fml 3.0pl#17]; post only (anyone can post)
X-ML-Info: If you have a question, send e-mail with the body
"help" (without quotes) to the address email@example.com;
see ruby-talk 44019 and subsequent responses
On Thu, 2002-08-22 at 08:38, firstname.lastname@example.org wrote:
With the laster cvs version, ruby gives warning
$ruby -e ‘“abc”.split("\r\n")’
-e:1: warning: string pattern instead of regexp; metacharacters
no longer effective.
What is reason for this change?