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");
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");
In detail:
- Compile print("first");.
- Compile BEGIN { ... }.
- Compile delete $INC{'ModX.pm'};.
- Compile use lib '../';.
- Execute use lib '../';.
- Compile use ModX;.
- Execute use ModX;.
- Execute BEGIN { ... }.
- Execute delete $INC{'ModX.pm'};.
- Compile print("last");.
- "Run phase" starts.
- Execute print("first");.
- Execute print("last");.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.