When a module become standard, that attitude changes somewhat.
But that's a really bad reason to make something part of the standard distribution. Then you'd put thousands of tiny little module into the standard distribution.
When does a module qualify as a standard module for you?
IMO, the only modules that should be part of the standard distributions are modules that:
- Have a tight integration with the perl core. (strict, IO::*, Unicode stuff, B::*, etc).
- Are necessary (or useful) to download and install other modules (CPAN, ExtUtils::*, etc).
- Anything that's needed to make Perl "Perl": Exporter, Carp, English, etc.
So, IMO, many modules already part of the core shouldn't be there:
Benchmark,
Getopt,
Memoize,
Switch, etc. Anything that lives, or can live, independently on CPAN doesn't need to be in the main Perl distribution.
Note that I'm not advocating to remove any module from the core. I'm only saying that mistakes from the past shouldn't be repeated.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.