in reply to Re: RFC: Should join subsume reduce?
in thread RFC: Should join subsume reduce?

And finally i think that it would be great to have such functionality in base perl without installing yet another module.

Just so you know this argument is a no-op. List::Util has been in core as of 5.8.x.

---
$world=~s/war/peace/g

Replies are listed 'Best First'.
Re^3: RFC: Should join subsume reduce?
by Aristotle (Chancellor) on Feb 23, 2006 at 12:22 UTC

    In fact, the argument is not just a no-op, it contradicts the sentiment: List::Util has been in core since 5.7.3 (to be precise), whereas this newfangled join would only appear in some future version of Perl – so if you wanted broader coverage, you’d use reduce anyway.

    Makeshifts last the longest.

      That's effectively an argument against adding any new features. Anybody who wanted broader coverage won't use, for example, the defined-or family of new features. Is it your position that there should be no new features added to Perl5?

      Caution: Contents may have been coded under pressure.

        I said that “I don’t want to install another module” is self-contradictory when the proposed way to avoid installing a new module involves install a new version of Perl – and self-defeating when the module in question actually is in core already.

        I’m not sure how you concluded that this means that new features should not be added to Perl.

        Makeshifts last the longest.

        Is it your position that there should be no new features added to Perl5?
        Is that an unreasonable position? Tread Perl5 as the stable branch of the language, and Perl6 as the experimental/growing version. It's not like the whole "reduce -> join" thing adds a whole lot of extra usability. Why tinker with a good thing? Am I missing something?