On what to add and omit from a CPAN module

At the very end of List::Util's docs we see:

The following are additions that have been requested, but I have been reluctant to add due to them being very simple to implement in perl

I think the point of a module is to

save someone from writing what is already written.
compartmentalize functionality so that you can...
keep the logic of the code focused on the task at hand

With that in mind, it does not matter how simple something is. What matters when deciding what to include in a module is

whether it has already been written
whether it will save someone else from writing something
whether it falls under the domain of the module at hand

So in my eyes, the functions that gbarr refused to add to List::Util should be there. And because they are not there, the utility of the module is less than it could be.

Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality

Comment on On what to add and omit from a CPAN module

Replies are listed 'Best First'.
Re: On what to add and omit from a CPAN module by Corion (Patriarch) on Aug 24, 2007 at 20:29 UTC
For a counterpoint, see the recent discussion on p5p regarding parent.pm, which was mostly about base.pm having too many magic features that fail in unexpected ways. The functions you want have been written and they live in List::MoreUtils, which is a bit inconvenient, but they are still there.	[reply]
Re^2: On what to add and omit from a CPAN module by princepawn (Parson) on Aug 24, 2007 at 20:38 UTC
Excellent point, so what we need is a pointer to List::MoreUtils from List::Util. Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality	[reply]
Re^3: On what to add and omit from a CPAN module by hossman (Prior) on Aug 24, 2007 at 21:44 UTC
it's in the "See Also" section of 1.19, released "10 Dec 2006"	[reply]
Re: On what to add and omit from a CPAN module by girarde (Hermit) on Aug 28, 2007 at 13:53 UTC
Seen that before. There is an Active Directory related module that does not provide for exporting object handles, just the object names. Since the next thing I always did with the name was bind to the object to get a handle, I went in and cut out the middle man.	[reply]