<?xml version="1.0" encoding="windows-1252"?>
<node id="760912" title="Re^3: On the rejected additions to List::Util" created="2009-04-29 12:14:27" updated="2009-04-29 12:14:27">
<type id="11">
note</type>
<author id="224409">
borisz</author>
<data>
<field name="doctext">
You do not need root access to use modules or install them. It is just a little more painful to install.

&lt; blockquote&gt;&lt;small&gt;
The question is more why List::MoreUtils has to exist at all. Why not put the functions in List::Util and do away with List::MoreUtils completely? Isn't it simpler and cleaner to have one utility module instead of several?
&lt;/small&gt;&lt;/blockquote&gt;

One reason is I use [cpan://List::MoreUtils] for years and do not plan to change all scripts. But a bit overdone, you ask to fold CPAN into the core?
A lot of my scripts use [cpan://XML::LibXML] and [cpan://DBI] and [cpan://HTML::Template]. I like to get them into the core too.

&lt;blockquote&gt;&lt;small&gt;
Do you think it's cleaner to have all the oneliners copied and pasted into the start of every script that uses them? Do you think it's simpler to have to remember which of several list utility libraries each basic function is in?
&lt;/small&gt;&lt;/blockquote&gt;

Often yes, since I have to read learn every silly simple function. Sure it is not a problem, if I add some simple handy functions to my script as well. I even like the split between the core functions and the handy glue.

Or you could use [cpan://List::AllUtils], but thats again not in the core.

&lt;!-- Node text goes above. Div tags should contain sig only --&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-224409"&gt;
Boris
&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
760703</field>
<field name="parent_node">
760736</field>
</data>
</node>
