There's no sharp border between a compiler and and an interpreter.
As you said, we often think of a compiler that takes the entire
source code, and produces something else (typically, before
running it), while an interpreter just looks at a small chunk
of the source at a time, and executes that before carrying on.
But compilers typically produce output that's being "interpreted".
Machine code is basically "interpreted". And a language that
has the ability to use "eval", can defer most of its "compilation"
to runtime, and have it compiled one chunk at a time.
I usually call a program that takes data in one format and
produces equivalent data in another format a compiler. That
means that 'gcc' is a compiler. But also 'dvips'. And perhaps
parts of 'perl' as well, although the other format is only
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.