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?= Newsgroups: comp.lang.java.programmer Subject: Re: questions re Javascript Date: Fri, 2 Oct 2015 22:47:25 -0400 Organization: Aioe.org NNTP Server Lines: 42 Message-ID: References: <83722e36-4afe-4077-b936-229450613698@googlegroups.com> 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:32772 On 9/27/2015 10:59 PM, Jerry Stuckle wrote: > On 9/27/2015 8:38 PM, Arne Vajhøj wrote: >> On 9/25/2015 9:56 AM, Jerry Stuckle wrote: >>> result is machine code. However, an additional step is required to link >>> in necessary libraries and other files. >>> >>> That does not mean the output of the compiler is not machine code. It's >>> just not executable-ready machine code. Once the link step is done, the >>> program is ready to run without any other program such as a jvm. >> >> Exactly. >> >> Which made the original claim of the output being directly executable >> false. >> >> It is not. >> >> The output from an additional step make it directly executable. > > I never said it was directly executable. Those are your words. I said > the output is machine code - which it is. Not true. Eternal hope wrote: #Well when I went to school (jeez, was it *that* long ago) a compiled #language was one where the compiler took source code as input and #produced native machine code that was directly executable on the #underlying hardware as output. Lew replied: #You misunderstood your classes. You replied: #No, he didn't. It was that way in my classes in the 1960's and 1970's, #also. Arne