The basic description is found in perlmod:
A "BEGIN" code block is executed as soon as possible, that is, the moment it is completely defined, even
before the rest of the containing file (or string) is parsed. You may have multiple "BEGIN" blocks
within a file (or eval'ed string) -- they will execute in order of definition. Because a "BEGIN" code
block executes immediately, it can pull in definitions of subroutines and such from other files in time
to be visible to the rest of the compile and run time. Once a "BEGIN" has run, it is immediately undefined and any code it used is returned to Perl's memory pool.
Also note that use has an implicit BEGIN block around it.
| [reply]
[d/l] |
Yeah I saw that text on the perlmod. But I didn't know that use was implicitly a BEGIN... so that makes more sense...
But anyone have any links to a more indepth write up of how the compiler works, like how it chooses what to compile first and all that...
| [reply] |
It's all in perlmod. Search for BEGIN, UNITCHECK, CHECK, INIT and END. But you should really read it all through.
There's more to be found in the perl sources... ;-)
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
| [reply] |