CORE(3pm)
πΈ NAME πΈ
CORE(3pm) from the Perl Programmers Reference Guide is literally the moment, bestie: CORE β Namespace for Perl's core routines π
β¨ SYNOPSIS β¨
BEGIN {
*CORE::GLOBAL::hex = sub { 1; };
}
print hex("0x50"),"\n"; # prints 1
print CORE::hex("0x50"),"\n"; # prints 80
CORE::say "yes"; # prints yes
BEGIN { *shove = \&CORE::push; }
shove @array, 1,2,3; # pushes on to @array
π¦ DESCRIPTION π¦
okay so the CORE namespace gives you access to the original built-in functions of Perl. The CORE package is built into Perl, and therefore you do not need to use or require a hypothetical CORE module prior to accessing routines in this namespace. no cap, it's already there π«Ά
A list of the built-in functions in Perl can be found in perlfunc. go off, perlfunc π
For all Perl keywords, a CORE:: prefix will force the built-in function to be used, even if it has been overridden or would normally require the feature pragma. Despite appearances, this has nothing to do with the CORE package, but is part of Perl's syntax. it's giving syntax main character energy, not package drama π
For many Perl functions, the CORE package contains real subroutines. This feature is new in Perl 5.16. You can take references to these and make aliases. However, some can only be called as barewords; i.e., you cannot use ampersand syntax (&foo) or call them through references. See the shove example above. These subroutines exist for all keywords except the following:
"__DATA__", "__END__", "and", "cmp", "default", "do", "dump", "else", "elsif", "eq", "eval", "for", "foreach", "format", "ge", "given", "goto", "grep", "gt", "if", "last", "le", "local", "lt", "m", "map", "my", "ne", "next", "no", "or", "our", "package", "print", "printf", "q", "qq", "qr", "qw", "qx", "redo", "require", "return", "s", "say", "sort", "state", "sub", "tr", "unless", "until", "use", "when", "while", "x", "xor", "y"
Calling with ampersand syntax and through references does not work for the following functions, as they have special syntax that cannot always be translated into a simple list (e.g., eof vs eof()):
"chomp", "chop", "defined", "delete", "eof", "exec", "exists", "lstat", "split", "stat", "system", "truncate", "unlink"
bestie, peek thateofvseof()glow-up π this is exactly why the special-syntax girlies can't always be called through refs.
π OVERRIDING CORE FUNCTIONS π
To override a Perl built-in routine with your own version, you need to import it at compile-time. This can be conveniently achieved with the subs pragma. This will affect only the package in which you've imported the said subroutine:
use subs 'chdir';
sub chdir { ... }
chdir $somewhere;
To override a built-in globally (that is, in all namespaces), you need to import your function into the CORE::GLOBAL pseudo-namespace at compile time:
BEGIN {
*CORE::GLOBAL::hex = sub {
# ... your code here
};
}
The new routine will be called whenever a built-in function is called without a qualifying package:
print hex("0x50"),"\n"; # prints 1
In both cases, if you want access to the original, unaltered routine, use the CORE:: prefix:
print CORE::hex("0x50"),"\n"; # prints 80
π AUTHOR π
This documentation provided by Tels <nospam-abuse@bloodgate.com> 2007. iconic behavior, honestly π
π SEE ALSO π
perlsub, perlfunc.
and that's the whole page, bestie π«Ά this one's from perl v5.42.3, dated 2026-11-03 β mwah π
π¦ where this page comes from
- alpine 3.24: perl-doc 5.42.3-r0 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms