Mind blowing Ruby String#split bug?
3 comments
Assuming by the notation you mean what jordsmi says and you mean:
Think about what's necessary when splitting up a row of CSV, say (or even some space limited logs or configs). You want that first 'missing' value to be represented in the output as it affects the position of later values. However, you don't need the final missing value represented as it has no significance - it's merely a trailing null value.
Also remember that Ruby has its heritage in Perl with methods like this, and Perl behaves similarly:
x = "*a*"
",a,".split(",") # => ["", "a"]
Think about what's necessary when splitting up a row of CSV, say (or even some space limited logs or configs). You want that first 'missing' value to be represented in the output as it affects the position of later values. However, you don't need the final missing value represented as it has no significance - it's merely a trailing null value.
Also remember that Ruby has its heritage in Perl with methods like this, and Perl behaves similarly:
perl -e "print join(':', split('\*', '*a*'));" # => ":a"For people not being able to recreate this is because he doesn't mean x = "a" he means x = "yay" with y being asterisks.
So
x = "yay"
x.split("y")
=> ["", "a"]
So
x = "yay"
x.split("y")
=> ["", "a"]
> x = "a"
=> "a"
> x.split('*')
=> ["", "a"]
Expected => ["", "a", ""] or ["a"]
It feels bizarre. Anyone has an explanation for this?