in reply to Re: repeated use of module and EXPORT
in thread repeated use of module and EXPORT

wow... you are right... that does work...
I had tried something very similar but I had the use L above the begin... I didn't think the location of the BEGIN would matter...
So... I am guessing that use statments are just like BEGIN blocks and thus happen in the order they are encoutnered.. is that right?
  • Comment on Re^2: repeated use of module and EXPORT

Replies are listed 'Best First'.
Re^3: repeated use of module and EXPORT
by rpelak (Sexton) on May 23, 2008 at 16:52 UTC
    actually... how is compilation order determined... or do you have any good links to documentation about compilation order and such... I tried to find it, but most links where about compilers that make exe's out of your perl... Randell

      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.

        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...