String#split "feature"

[Gary Yngve]

[Note: parts of this message were removed to make it a legal post.]

Just got bitten by some functionality of split w/ grouped patterns:

(in ruby 1.8.6...)

"foo bar baz".split(/bar/) => ["foo ", " baz"]
"foo bar baz".split(/(bar)/)

=> ["foo ", "bar", " baz"]

The 1.8 docs are silent on this, but the 1.9 docs at least say
"If pattern contains groups, the respective matches will be returned in the
array as well. "

This "feature" surprised the heck out of me.. Anyone know if this
functionality is intentional (from the enduser standpoint), or rather a
byproduct of implementation details?

Anyhoo, if anyone else gets weird behavior for string split including the
pattern, or with groups in the pattern, maybe you'll remember this or maybe
google will tell you about this.

Thanks,
-Gary

 

[7stud --]

The 1.8 docs are silent on this, but the 1.9 docs at least say
"If pattern contains groups, the respective matches will be returned in
the
array as well. "

pickaxe2 p.619:
=====
split
...
...
If pattern includes groups, these groups will be included in the
returned values.
...
=====

This "feature" surprised the heck out of me.. Anyone know if this
functionality is intentional (from the enduser standpoint), or rather a
byproduct of implementation details?

It can be a really handy feature. python's regex split() function works
the same way.

 

[Rob Biedenharn]

pickaxe2 p.619:
=====
split
...
...
If pattern includes groups, these groups will be included in the
returned values.
...
=====

Interestingly, this feature is described in String#scan, but the ri
docs for my Apple-provided ruby do not have the sentence for
String#split.

$ ruby -v
ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]

-Rob

It can be a really handy feature. python's regex split() function
works
the same way.

Rob Biedenharn http://agileconsultingllc.com
(e-mail address removed)

 

[F. Senault]

Le 10 février 2009 à 21:20, Gary Yngve a écrit :

This "feature" surprised the heck out of me.. Anyone know if this
functionality is intentional (from the enduser standpoint), or rather a
byproduct of implementation details?

Anyhoo, if anyone else gets weird behavior for string split including the
pattern, or with groups in the pattern, maybe you'll remember this or maybe
google will tell you about this.

It's quite useful. Note that you can always use non-capturing groups
(the (?:expr) construct) if you don't want them :
=> ["one", ",", "two", "and", "three"]
=> ["one", "two", "three"]

Fred