Here are some benchmark results to peruse...
Not too surprising (in fact, I would have been shocked had there really been a substantial difference).Benchmark: timing 100000 iterations of Deparses, for... Deparsed: 5 wallclock secs ( 4.43 usr + 0.00 sys = 4.43 CPU) for: 6 wallclock secs ( 4.39 usr + 0.00 sys = 4.39 CPU)
Just thinking of really low-level code, the Deparse version is really just the "under-the-hood" action of a for loop. Think about assembly (pseudo) code:
So, the Deparsed code is just a closer representation of the low-level code.# Warning: I make no claims to know assembly, this is an example only +:-) mov bx 0 ; Initialize our loop variable mov ax, 10 ; Remember our exit condition top: ; Mark the top of the loop jnle last: ; Quit if bx is not less than ax print bx ; Do the body of the loop add bx 1 ; Add one to the loop variable jmp top: ; go to the top of the loop last:
The continue block (from perlsyn)
If there is a continue BLOCK, it is always executed just before the conditional is about to be evaluated again, just like the third part of a for loop in C. Thus it can be used to increment a loop variable, even when the loop has been continued via the next statement (which is similar to the C continue statement).So, the continue block executes once per iteration of the loop. Why would you use one yourself?
Russ
Brainbench 'Most Valuable Professional' for Perl
In reply to RE: why does a for loop parse like this?
by Russ
in thread why does a for loop parse like this?
by eduardo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |