Re^2: Perl compiler request - flogging the dead horse!

OK, I'll bite. Please explain how a compiler can deal with this:

while (my $line = <>) {
  print eval $line;
}
[download]

Time flies when you don't know what you're doing

Comment on Re^2: Perl compiler request - flogging the dead horse! Download Code

Replies are listed 'Best First'.
Re^3: Perl compiler request - flogging the dead horse! by Anonymous Monk on Feb 07, 2014 at 21:52 UTC
OK, I'll bite. Please explain how a compiler can deal with this: By not dealing with it, see Perl 5 Optimizing Compiler, Part 9: RPerl.org & The Low-Magic Perl Commandments	[reply]
Re^4: Perl compiler request - flogging the dead horse! by FloydATC (Deacon) on Feb 11, 2014 at 07:13 UTC
OK, so basically it can compile "P" but "erl" isn't supported. -- FloydATC Time flies when you don't know what you're doing	[reply]
Re^5: Perl compiler request - flogging the dead horse! by Will_the_Chill (Pilgrim) on Feb 20, 2014 at 07:32 UTC
Compile P and link it back in, erl never knows the difference but your code runs way faster.	[reply]
Re^5: Perl compiler request - flogging the dead horse! by Will_the_Chill (Pilgrim) on Feb 20, 2014 at 07:36 UTC
Also, "isn't supported" is wrong; P is the only part that can be statically compiled, erl must be dynamically interpreted. Eventually we can do JIT dynamic compilation on erl and combine with static compilation on P to get the fastest possible, then we will be faster than Java and close to C. Then I will stop flogging the "dead horse", because it will be a live Camel and Roadrunner!	[reply]