in reply to Re: On the rejected additions to List::Util
in thread On the rejected additions to List::Util

Just that some people want an abstraction isn't a reason to put in List::Util. Feel free to create a module with the abstraction you want and distribute it.
  • Comment on Re^2: On the rejected additions to List::Util

Replies are listed 'Best First'.
Re^3: On the rejected additions to List::Util
by Roy Johnson (Monsignor) on Apr 28, 2009 at 20:14 UTC
    What are legitimate reasons to put it in List::Util?

    Having List::Utils, List::MoreUtils, List::EvenMoreUtils, List::SomeMoreUtilsByMe, List::AnotherCoupleUtilsTheyForgot, etc. seems like it might be a Bad Thing. Better to have basic list utilities in one List::Utils module, I think. And the reason they're not included? They're "too basic".

    It's a perfectly good reason to include them in List::Util. It's not an absolute mandate that they be included, but it is a reason.


    Caution: Contents may have been coded under pressure.
        But where's NestedLoop and MapCar!