Re^3: Strange issues with mod

Thanks for that correction. I didn't know nested BEGIN blocks execute in "reverse order". It seems completely unintuitive, illogical, and I don't like it but at least now I know :-)

update:

perl -e 'print "a"; BEGIN { print "b"; BEGIN { print "c" }}'
[download]

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^3: Strange issues with mod_perl and use lib Download Code

Replies are listed 'Best First'.
Re^4: Strange issues with mod_perl and use lib by ikegami (Patriarch) on May 18, 2007 at 14:17 UTC
It's really not unintuitive. It's just like nested `for` loops. It's just like recursion. The most nested item always completes first. Nested `BEGIN` blocks and `use` statements are only executed in reverse order if you look at the start of the statement. They're executed in-order if you look at the whole statement or the end of the statement. How can you execute something before it's compiled?	[reply] [d/l] [select]