Re^3: BEGIN and compile-time

but the more correct way is to think of run-time and compile-time as a per-block thing.

Quite so, ++ (Per-statement, even, in the case of use.)

print("first");
BEGIN {
  delete $INC{'ModX.pm'};
  use lib '../';
  use ModX;
}
print("last");
[download]

gets executed in the following order

use lib '../';           # Before "delete" because of "use"
use ModX;                # Before "delete" because of "use"
delete $INC{'ModX.pm'};  # Before "first" because of "BEGIN"
print("first");
print("last");
[download]

In detail:

Compile print("first");.
Compile BEGIN { ... }.
1. Compile delete $INC{'ModX.pm'};.
2. Compile use lib '../';.
3. Execute use lib '../';.
4. Compile use ModX;.
5. Execute use ModX;.
Execute BEGIN { ... }.
1. Execute delete $INC{'ModX.pm'};.
Compile print("last");.
"Run phase" starts.
Execute print("first");.
Execute print("last");.

Comment on Re^3: BEGIN and compile-time Select or Download Code

Replies are listed 'Best First'.
Re^4: BEGIN and compile-time (per statement) by tye (Sage) on Nov 02, 2006 at 17:25 UTC
but the more correct way is to think of run-time and compile-time as a per-block thing. (Per-statement, even, in the case of use.) More than just in the case of use. Certainly "my" statements have separate compile-time and run-time effects. "sub" declarations also have a compile-time impact as do "package" statements (as demonstrated in Object lesson). There may be others as well that just don't spring immediately to my mind. See Re^5: What is the scope of BEGIN? Or... when does it "begin?" (steps). Each statement has one "compile time" and zero or more "run times". I never talk about the one "compile time" or the one "run time" as that makes no sense to me. I'd not say '`"Run phase" starts`', for example. There is behavior that is triggered between when the main script source code has finished being compiled and the resulting non-sub code begins to be run. (Since I've never found a need to use CHECK / INIT blocks, I've never bothered to figure out and internalize how they are really scheduled, however.) But it makes no sense to me to say "CHECK code blocks are run [...] before run time begins" when lots of code has already seen its "run time" (and been run) before that. - tye	[reply]
Re^5: BEGIN and compile-time (per statement) by ikegami (Patriarch) on Nov 02, 2006 at 17:37 UTC
I'd not say '"Run phase" starts', for example. Notice the quotes. I included it to show how meaningless/misleading the term is, showing stuff being run before this so-called "runtime" phase. Thanks for the clarification.	[reply]