note
Erez
<p align="center"><i>Perl is an interpreted language ... Perl code is executed by a virtual machine that is itself a binary executable for the native hardware of the host</i></p>
<p>No, and No.<br>
Quote Tom Christiansen ([href://http://www.perl.com/doc/FMTEYEWTK/comp-vs-interp.html|FMTEYEWTK about Compilation vs Interpretation in Perl]):</p>
<p align="center"><i>The perl executable ... has two distinct stages ... It compiles your perl program source into a parse tree. This compiler then performs various optimizations such as ... loading in certain library definitions ...<br>
Next comes the backend, which is certainly an interpreter of sorts; let's call it a PP interpreter for now, just because. While what it actually executes is a parse tree and not byte code per se, still we would not go wrong in classifying this backend as a byte-code interpreter (like java or python). This is useful in particular when it comes to distinguishing these languages from "pure" interpreters.</i></p>
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-618967">
<p><font size="1">"A core tenant of the greater Perl philosophy is to trust that the developer knows enough to solve the problem" - <a href="http://perlbuzz.com/2008/11/a-case-for-catalyst.html">Jay Shirley, A case for Catalyst</a></font>.</p>
</div></div>
729070
729077