Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re: On Compilation, Call Trigger Policy: Now vs Inline

by sh1tn (Priest)
on Dec 06, 2007 at 13:45 UTC ( #655400=note: print w/ replies, xml ) Need Help??


in reply to On Compilation, Call Trigger Policy: Now vs Inline

It is written:If you think of an eval STRING as a call back from the interpreter to the compiler, then you might think of a BEGIN as a call forward from the compiler into the interpreter. Both temporarily put the current activity on hold and switch modes of operation.

Pretty self-explanatory.

print "start main running here\n"; eval "BEGIN{print qq(BEGIN: before eval compilation at run-time +\n)} END{print qq(END: from eval STRING\n)}"; eval {BEGIN{print qq(BEGIN: before eval compilation at compile-t +ime\n)} END{print qq(END: from eval BLOCK\n)}}; END { print "END: done running\n" } BEGIN { print "BEGIN: still compiling\n" }



Comment on Re: On Compilation, Call Trigger Policy: Now vs Inline
Download Code
Re^2: On Compilation, Call Trigger Policy: Now vs Inline
by ian (Beadle) on Dec 06, 2007 at 17:26 UTC
    I'm in agreement about the straightforwardness of call back and call forward with respect to interpreter->compiler and compiler->interpreter; it's the difference between the call trigger policy of "Now" vs "Inline" that's confusing to me. Is it merely that BEGIN is always triggered at the beginning of the line versus an eval which can be triggered anywhere within one?
    -- Ian Tegebo

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (9)
As of 2014-07-28 13:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (197 votes), past polls