comment on

I'm still confused. I don't see how, if the "new" happens before "has", ..:)blah..

because line 7 (new) and line 10 (say) come before line 15 (has) and all three come after each use line

read use , require, do, eval, BEGIN, UNITCHECK, CHECK, INIT and END

Re: Non-traditional, Line by Line Compilation in Perl

#!/usr/bin/perl

# begincheck

print         "10. Ordinary code runs at runtime.\n";

END { print   "16.   So this is the end of the tale.\n" }
INIT { print  " 7. INIT blocks run FIFO just before runtime.\n" }
UNITCHECK {
print       " 4.   And therefore before any CHECK blocks.\n"
}
CHECK { print " 6.   So this is the sixth line.\n" }

print         "11.   It runs in order, of course.\n";

BEGIN { print " 1. BEGIN blocks run FIFO during compilation.\n" }
END { print   "15.   Read perlmod for the rest of the story.\n" }
CHECK { print " 5. CHECK blocks run LIFO after all compilation.\n" }
INIT { print  " 8.   Run this again, using Perl's -c switch.\n" }

print         "12.   This is anti-obfuscated code.\n";

END { print   "14. END blocks run LIFO at quitting time.\n" }
BEGIN { print " 2.   So this line comes out second.\n" }
UNITCHECK {
print " 3. UNITCHECK blocks run LIFO after each file is compiled.\n"
}
INIT { print  " 9.   You'll see the difference right away.\n" }

print         "13.   It merely _looks_ like it should be confusing.\n"
+;

__END__
 1. BEGIN blocks run FIFO during compilation.
 2.   So this line comes out second.
 3. UNITCHECK blocks run LIFO after each file is compiled.
 4.   And therefore before any CHECK blocks.
 5. CHECK blocks run LIFO after all compilation.
 6.   So this is the sixth line.
 7. INIT blocks run FIFO just before runtime.
 8.   Run this again, using Perl's -c switch.
 9.   You'll see the difference right away.
10. Ordinary code runs at runtime.
11.   It runs in order, of course.
12.   This is anti-obfuscated code.
13.   It merely _looks_ like it should be confusing.
14. END blocks run LIFO at quitting time.
15.   Read perlmod for the rest of the story.
16.   So this is the end of the tale.
[download]

Maybe I shouldn't be worrying, but I'm scared there's a trap lying in wait for me.

:D while( $fear ){ LEARN: { perldoc(); test(); }; $fear--; }

In reply to Re^3: Moo error message not understood (begincheck.pl) by Anonymous Monk
in thread Moo error message not understood by davies

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks