Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Translator, Compiler, Interpreter and Java Date: Mon, 5 Oct 2015 22:10:49 -0400 Organization: Aioe.org NNTP Server Lines: 29 Message-ID: References: <00e382b4-e046-4b84-aeda-ba718a9f19be@googlegroups.com> NNTP-Posting-Host: 1lM8B9/qdtKBc/uIRK2Gjw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:32817 On 10/5/2015 2:23 PM, Jerry Stuckle wrote: > On 10/5/2015 1:58 PM, Lew wrote: >> On Monday, October 5, 2015 at 5:45:06 AM UTC-7, Jerry Stuckle wrote: >>> The JVM from Oracle, for instance. On Windows, it's called java.exe. >> >> That's not a Java interpreter. It does not interpret Java. >> >> You have to run Java code through "javac.exe" (on Windows) or "javac" (other platforms) before "java"/"java.exe" can handle it. >> >> So again I ask, what *Java* interpreter can interpret bytecode? >> >> byecode != Java. Different syntax, different semantics, different architecture. > > Wrong again on all parts. Nope. He is correct that the JVM does not interpret Java. He is correct that Java need to be send through the Java compiler before the JVM can handle it. It don't think it is possible to be wrong with a question. bytecode != Java is also correct. Arne