Issue #5400 has been updated by Andrew Grimm.


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?
----------------------------------------
Feature #5400: Remove flip-flops in 2.0
http://redmine.ruby-lang.org/issues/5400

Author: Magnus Holm
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 2.0


Nobody knows them. Nobody uses them. Let's just get rid of flip-flops, shall we?


-- 
http://redmine.ruby-lang.org