In Chapter 18 of the Camel Book it is said:

1. The compilation phase
(...) BEGIN blocks are handed off to the interpreter to be run as soon as they are parsed, which effectively runs them in FIFO order. (...) Any CHECK, INIT and END blocks are scheduled by the compiler for delayed execution. (...) At the end of this phase, the interpreter is again called up to execute any scheduled CHECK blocks in LIFO order.

2. The code generation phase.
CHECK blocks are installed by code generators, so this optional phase occurs when you explicitly use one of the code generators. These convert the compiled (but not yet run) program into C source code or serialized Perl byte codes.

4. The Execution phase.
(...) At the start of this phase, before your main program gets to run, all scheduled INIT blocks are executed in FIFO order. Then your main program is run. (...) When your main program finishes, any delayed END blocks are finally executed, this time in LIFO order.

Such are the words which can be found in the Camel Book.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law


In reply to Re: What is an INIT block? by CountZero
in thread What is an INIT block? by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.