Path: csiph.com!au2pb.net!feeder.erje.net!1.eu.feeder.erje.net!nntpspool01.opticnetworks.net!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Translator, Compiler, Interpreter and Java
Date: Fri, 2 Oct 2015 22:41:00 -0400
Organization: Aioe.org NNTP Server
Lines: 30
Message-ID: <munf7v$gtn$4@speranza.aioe.org>
References: <mu2j1a$34n$1@dont-email.me> <mu3lpf$lq7$1@dont-email.me> <mua4au$g63$1@speranza.aioe.org> <muaau2$g6h$3@dont-email.me>
NNTP-Posting-Host: 1lM8B9/qdtKBc/uIRK2Gjw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:32771

On 9/27/2015 11:09 PM, Jerry Stuckle wrote:
> On 9/27/2015 9:15 PM, Arne Vajhøj wrote:
>> On 9/25/2015 10:32 AM, Jerry Stuckle wrote:
>>> Languages such as Java are somewhere in between.  There is a "compiler"
>>> (more properly called a "translator", IMHO) which converts the source
>>> code to a byte code.  But this byte code does not run natively; it
>>> requires another program (like the jvm) to interpret the code and
>>> convert it to code which can be executed by the processor.  But because
>>> this interpretation must be performed every time the program is
>>> executed, Java is considered an interpreted language.
>>
>> The argument that having to run a compiler at every program
>> invocation makes the language non-compiled seems rather non-intuitive.
>>
>> :-)
>
> Who (besides you) ever said you had to run a compiler at every program
> invocation?

You did.

"to interpret the code and convert it to code which can be executed by 
the processor"

This process is what is called JIT compilation done by a JIT compiler.

Arne