For over a week now I am preparing the next List::MoreUtils release. It takes so long because I am incorporating all stuff from List::MoreUtil into it. For each new function I had to write an equivalent XSUB and some of the turned out to be a bit tricky.
Then I noticed that List::MoreUtil's tests (that I simply took over) are incomplete in that they don't test some of the key characteristis of each function. Some map-like functions pass aliases to the original values to their code argument. Others don't. As it happened, I also noticed that the pure-Perl implementation and the XSUB one sometimes differed with respect to this so I had to make that consistent, too.
The only thing left is now copying the documentation for these functions over from List::MoreUtil. Most probably I will be deeply unhappy with it so I might end up rewriting it.
how about adding... (Score:1)
uniq() for returning unique values from a list
uniq_ordered() for returning unique values from a list in the order that they were first seen
stats() which will return max, min, ave, tot, count for a list
See http://www.perlmonks.org/?node_id=407834 for background.
Cheers
L~R
Re:how about adding... (Score:2)
avgis already getting dangerously close to statistical functionality. Not that this would be fundemantally wrong in a list-module, but then people might come and ask for functions to calculate the quadratic mean or geometric mean as well.As for
uniqanduniq_ordered, the first is no more computational work than the second from an XS point of view (as there are no hash-slices in C so one needs to loop anyway).uniqI could add.I am not convinced that
statsis so terribly useful.maxandminare already in