3 ms·
I don't trust Ruby for text processing anymore. The removal of the flip-flop operator, which is a fundamental tool in text processing, sent a very clear signal
by pizza234 7y ago
I don't trust Ruby for text processing anymore.
The removal of the flip-flop operator, which is a fundamental tool in text processing, sent a very clear signal about the Ruby direction (that is, to be "The Rails language" and nothing else).
How can one be sure now, that all the functionality you've mentioned (and more) won't be removed as well?
Perl can be ugly, but its foundation in text processing are established.
- byroot 7y ago> The removal of the flip-flop operator Well that never happened. It was deprecated with the intention to remove it, but they backtracked: https://bugs.ruby-lang.org/issues/5400#note-25 https://bugs.ruby-lang.org/issues/5400#note-25
- pizza234 7y agoInteresting. The discussion, although minimal, lasted years, then closed pretty quickly. Good for Ruby :-)
- faitswulff 7y agoI'm glad Ruby takes community feedback seriously, for the most part - most recently the pipeline operator and the named block parameters, for instance.
- cutler 7y agoI heard Matz is going to remove the Perl special variables in Ruby 3.0. Can't think what the fuss is all about. They're pretty useful in command-line Ruby. I moved from Perl to Ruby so I will be sad to see this bit of Perl heritage removed from Ruby. I mean for what gain?
- byroot 7y agoOnly a very small subset of them: https://bugs.ruby-lang.org/issues/14240 https://bugs.ruby-lang.org/issues/14240 $/ input record separator (default argument for "gets") $\ output record separator ("print" prints it at last) $, default separator for Array#join and print $; default separator for String#split As for the gain it's because these variables globally change the behavior of important core methods. They really aren't that useful, but can easily cause havoc.