Without looking, I'd bet that there are one or more subsection of each that are not used by every use of the main module and that these could be factored out into sub module(s) and required when required rather than loading everything always.

CGI.pm certainly could do this, even allowing for the fact that it generates a lot of it's function on demand. I fully understand the motivations and temptations for people that want to "just parse the options string and print a header or two". If the major :xxx load options to CGI.pm effectively turned into

require 'CGI::HTML4' if %opts{ html4 };
require 'CGI::download' if $opts{ download };
[download]

I don't think it would do any harm at all.

The only downside of that is that Perl doesn't support a use Foo::*; syntax, though writing a use wild 'Foo::*'; pragma would be possible I think.

I have a general preference for lots of small files, rather than 1 or 2 huge ones. With editors that can hold multiple files and provide search/replace/index across all workspaces, I find the ability to be working in several places at once in different files very useful. My editor also supports having multiple views of a single file, but I very rarely use it. Years ago I used a very excellent folding editor which encouraged you to put lots of stuff in a single file and use a collapsed view to navigate. It worked great, but then compiling became a chore.

I like to keep as much as possible to do with one unit of code in the same file as I can. Code. Interface (user) docs. Breif modification history. Unit tests. This becomes unweildy where the units are too all encompassing.

For a very large OO module, I would seriously consider putting the class definition, initialisation, constructors and destructors into one file and moving the methods into one or more separate files and loading them as procedures.

Anyway, it's just a preference, not an edict. The OP will doubtless make up there own mind on the matter.

I'll grant that CGI is not the best example of 'doing one and only one thing'.

That's a very interesting take on code organization. I'd love to see a Meditation on that topic, if you wouldn't mind.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

I liked the idea of wild.pm so much, that I wrote one:

package wild;
$VERSION = 0.01;

use strict;
use Carp;
use Module::Find;


sub import {
    shift;

    foreach my $module (@_) {
        # at the moment we only support '...::*'
        if ($module =~ /(.+)::\*$/) {
            usesub $1;
        } else {
            croak "'$module' not supported, only '...::*'";
        }
    }
}


1;
[download]

Currently it uses Module::Find.
And here is a little test script.

#!/usr/bin/perl -w

use strict;
use Data::Dumper;

BEGIN {
    print Dumper(\%INC);
}

use wild 'HTML::*';

print Dumper(\%INC);
[download]

Have fun,
Uwe

Neat++;

Have fun,

I think I will :)

---

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon