Hi,

Under the current plan, I am not going to remove flip-flop from 2.0,
since we are not going to made incompatible changes anytime soon.  We
have to wait until 3.0.

							matz.

In message "Re: [ruby-core:40043] [Ruby 1.9 - Feature #5400] Remove flip-flops in 2.0"
    on Sat, 8 Oct 2011 11:51:50 +0900, Andrew Grimm <andrew.j.grimm / gmail.com> writes:

|I'll be a little sad if the flip flop operator is removed, but it is a Perlism, and Ruby is gradually getting rid of Perlisms. I suspect it won't be around in 100 years time, and I've heard that flip-flops aren't mentioned in the Ruby specification.
|
|When I mentioned flip-flops (and Rubinius' failure to support them) in my talk at RubyKaigi 2011, the response of some was "What's the flip flop operator?"
|
|If the feature is removed, how will Ruby treat existing code that uses the flip-flop operator?
|
|Will it convert it into a literal range, and raise an ArgumentError? (false)..(true) raises an ArgumentError
|
|Or will it explain that flip-flops are no longer supported?