Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re^3: Moo error message not understood (begincheck.pl)

by Anonymous Monk
on Jan 17, 2014 at 20:20 UTC ( #1071015=note: print w/ replies, xml ) Need Help??


in reply to Re^2: Moo error message not understood (BEGIN block missing)
in thread Moo error message not understood

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.

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--; }


Comment on Re^3: Moo error message not understood (begincheck.pl)
Select or Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1071015]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (4)
As of 2014-07-31 01:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (244 votes), past polls