MODULE::CORELIST(3perl)

πŸ’– Module::CoreList β€” what modules shipped with versions of perl πŸ’–

okay bestie, this is the Module::CoreList(3perl) page from the Perl Programmers Reference Guide, and it's literally the lore archive of which modules came bundled with which perl. sit down, hydrate, let's go ✨


🌸 NAME 🌸

Module::CoreList β€” what modules shipped with versions of perl 🫢


✨ SYNOPSIS ✨

use Module::CoreList;

print $Module::CoreList::version{5.00503}{CPAN}; # prints 1.48

print Module::CoreList->first_release('File::Spec');
# prints 5.00405

print Module::CoreList->first_release_by_date('File::Spec');
# prints 5.005

print Module::CoreList->first_release('File::Spec', 0.82);
# prints 5.006001

if (Module::CoreList::is_core('File::Spec')) {
  print "File::Spec is a core module\n";
}

print join ', ', Module::CoreList->find_modules(qr/Data/);
   # prints 'Data::Dumper'
print join ', ',
         Module::CoreList->find_modules(qr/test::h.*::.*s/i, 5.008008);
   # prints 'Test::Harness::Assert, Test::Harness::Straps'

print join ", ", @{ $Module::CoreList::families{5.005} };
   # prints "5.005, 5.00503, 5.00504"

like. look at that. no cap, that's the whole vibe in nine little snippets πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Module::CoreList hands you the receipts on which core and dual-life modules shipped with each version of perl. every single one. it's giving encyclopedia but make it slay.

it gives you a bunch of mechanisms for querying this info, so you can pick whichever one matches your mood:

  • there's a utility called corelist that comes with this module, and it's the convenient way to query from the command-line πŸŽ€
  • there's a functional programming API for programmers who wanna query the info in code
  • and programmers may also go straight at the contained hash structures themselves to find the relevant info

pick your fighter. all three are valid. iykyk πŸ’œ


πŸ‘‘ FUNCTIONS API πŸ‘‘

these are the functions that are available, and the way that… you can call them either as plain functions or as class methods, bestie:

Module::CoreList::first_release('File::Spec'); # as a function

Module::CoreList->first_release('File::Spec'); # class method

same energy, two outfits. here's the whole roster:

  • first_release( MODULE ) β€” behaviour since version 2.11. you gotta pass a MODULE name as an argument, and it returns the perl version where that module first appeared in core, ordered by perl version number. if that module is not in core you get undef (in scalar context) or an empty list (in list context). no module, no entry, no drama πŸ’€
  • first_release_by_date( MODULE ) β€” takes a MODULE name as an argument, and returns the perl version where that module first appeared in core, but ordered by release date. same deal as above: undef in scalar context, empty list in list context, if the module isn't in core.
  • find_modules( REGEX, [ LIST OF PERLS ] ) β€” takes a regex as an argument and returns a list of modules that match the regex you gave. if you only pass a regex, it applies to all modules in all perl versions. optionally you can hand it a list of perl versions to limit the regex search to just those πŸŽ€
  • find_version( PERL_VERSION ) β€” takes a perl version as an argument. upon successful completion it returns a reference to a hash. each element of that hash has a key which is the name of a module (e.g., 'File::Path') shipped with that version of perl, and a value which is the version number (e.g., '2.09') of that module which shipped with that version of perl. returns undef otherwise. πŸ’…
  • is_core( MODULE, [ MODULE_VERSION, [ PERL_VERSION ] ] ) β€” available in version 2.99 and above. returns true if MODULE was bundled with the specified version of Perl. you can optionally specify a minimum version of the module, and you can also specify a version of Perl. if a version of Perl isn't specified, is_core() will use the numeric version of Perl that is running (ie $]). if you wanna specify the version of Perl but don't care about the version of the module, pass undef for the module version ✨
  • is_deprecated( MODULE, PERL_VERSION ) β€” available in version 2.22 and above. returns true if MODULE is marked as deprecated in PERL_VERSION. if PERL_VERSION is omitted, it defaults to the current version of Perl.
  • deprecated_in( MODULE ) β€” available in version 2.77 and above. returns the first perl version where the MODULE was marked as deprecated. returns undef if the MODULE has not been marked as deprecated. πŸ™ˆ
  • removed_from( MODULE ) β€” available in version 2.32 and above. takes a module name as an argument, returns the first perl version where that module was removed from core. returns undef if the given module was never in core or remains in core.
  • removed_from_by_date( MODULE ) β€” available in version 2.32 and above. takes a module name as an argument, returns the first perl version by release date where that module was removed from core. returns undef if the given module was never in core or remains in core.
  • changes_between( PERL_VERSION, PERL_VERSION ) β€” available in version 2.66 and above. given two perl versions, this returns a list of pairs describing the changes in core module content between them. the list is suitable for storing in a hash. the keys are library names and the values are hashrefs. each hashref has an entry for one or both of "left" and "right", giving the versions of the library in each of the left and right perl distributions.

for example, it might return these data (among others) for the difference between 5.008000 and 5.008001:

'Pod::ParseLink'  => { left => '1.05', right => '1.06' },
'Pod::ParseUtils' => { left => '0.22', right => '0.3'  },
'Pod::Perldoc'    => {                 right => '3.10' },
'Pod::Perldoc::BaseTo' => {            right => undef  },

this shows us two libraries being updated and two being added, one of which has an undefined version in the right-hand side version. iconic behaviour honestly πŸ”₯


πŸŽ€ DATA STRUCTURES πŸŽ€

these are the hash data structures that are available, and yes they're all just sitting there waiting for you:

  • %Module::CoreList::version β€” a hash of hashes that is keyed on perl version as indicated in $]. the second level hash is module => version pairs.

note, it is possible for the version of a module to be unspecified, whereby the value is undef, so use exists $version{$foo}{$bar} if that's what you're testing for. do not come for me if you checked the value instead, bestie, it's undef, it's always been undef 😭

starting with 2.10, the special module name "Unicode" refers to the version of the Unicode Character Database bundled with Perl.

  • %Module::CoreList::delta β€” available in version 3.00 and above. it is a hash of hashes that is keyed on perl version. each keyed hash will have the following keys:
delta_from - a previous perl version that the changes are based on
changed    - a hash of module/versions that have changed
removed    - a hash of modules that have been removed
  • %Module::CoreList::released β€” keyed on perl version, this contains ISO formatted versions of the release dates, as gleaned from perlhist. πŸ—“οΈ
  • %Module::CoreList::families β€” new, in 1.96, a hash that clusters known perl releases by their major versions. it's giving family tree, it's giving ancestry.com for perl releases 🧚
  • %Module::CoreList::deprecated β€” a hash of hashes keyed on perl version and on module name. if a module is defined it indicates that that module is deprecated in that perl version and is scheduled for removal from core at some future point. πŸ’€
  • %Module::CoreList::upstream β€” a hash that contains information on where patches should be directed for each core module.

UPSTREAM indicates where patches should go. undef implies that this hasn't been discussed for the module at hand. "blead" indicates that the copy of the module in the blead sources is to be considered canonical, "cpan" means that the module on CPAN is to be patched first. "first-come" means that blead can be patched freely if it is in sync with the latest release on CPAN.

  • %Module::CoreList::bug_tracker β€” a hash that contains information on the appropriate bug tracker for each core module.

BUGS is an email or url to post bug reports. for modules with UPSTREAM => 'blead', use <mailto:perl5-porters@perl.org>. rt.cpan.org appears to automatically provide a URL for CPAN modules; any value given here overrides the default: <http://rt.cpan.org/Public/Dist/Display.html?Name=$ModuleName>


⚠️ CAVEATS ⚠️

okay babes, listen up, coverage check:

  • Module::CoreList currently covers the 5.000, 5.001, 5.002, 5.003_07, 5.004, 5.004_05, 5.005, 5.005_03, 5.005_04 and 5.7.3 releases of perl.
  • all stable releases of perl since 5.6.0 are covered.
  • all development releases of perl since 5.9.0 are covered.

so if you're out here querying something older than that, that's on the historical record, not on us 🫢


🌈 HISTORY 🌈

moved to Changes file. yeah. that's it. that's the whole section. it's giving "we outsourced the lore" ✨


πŸ’œ AUTHOR πŸ’œ

Richard Clamp <richardc@unixbeard.net>

currently maintained by the perl 5 porters <perl5-porters@perl.org>. legends, both. πŸ‘‘


⭐ LICENSE ⭐

Copyright (C) 2002-2009 Richard Clamp. All Rights Reserved.

this module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. slay, legally. πŸ’…


πŸ”₯ SEE ALSO πŸ”₯


k that's the whole page bestie, you ate it, no crumbs πŸ“ this was the Module::CoreList(3perl) page from perl v5.44.0, dated 2026-10-17 β€” go forth and query, mwah πŸ’–πŸŽ€

πŸ“¦ where this page comes from
  • arch rolling: perl 5.44.0-1 Β· Artistic-1.0-Perl AND GPL-1.0-or-later
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms