On Wed Dec 13 10:04:51 2017, PETDANCE wrote:
Show quoted text> I'm sorry if I opened a political can of worms here.
As far as I can say: you didn't open a political can of worms :)
Unfortunately there is neither noteworthy communication between
List::Util and List::MoreUtils nor between PEVANS and myself.
Show quoted text> All I'm asking for an explanation in the docs explaining the
> differences, if any, between List::Util::first and
> List::MoreUtils::firstval. I have a codebase that uses
> List::Util::first in some places and List::MoreUtils::firstval. I'd
> like to standardize on one or the other. I'm just looking for
> clarification in the docs that they work the same, or how they're
> different if not. I'm sure I can't be the only one in this situation.
You're the one and only who asked. Finally I can't do more than you
and have a look into List::Util documentation and from there I'd say,
they're the same.
I see that first() is mentioned around 2001 for release 1.03 first time
in List:Util and can imagine that Tassilo introduced it to complete
the quadruple of firstidx/firstval/lastidx/lastval - but finally no one
knows and I don't know anyone to ask.
That leads me back to my list how to choose the best function
for your needs.
From what you had written, I suggest use List::Util::first - it's in core
and gets more love from core hackers than LMU.
If you want a clarification, by definition List::Util is the better
place. Paul is taking suggestions and ideas from L::MU into L::U
and provides usually his own implementation.
Best regards,
Jens