Path: csiph.com!news.mixmin.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: Thu, 24 Sep 2015 23:00:27 -0400 Organization: Aioe.org NNTP Server Lines: 51 Message-ID: References: <83722e36-4afe-4077-b936-229450613698@googlegroups.com> <47d69c57-6ce4-4f35-9e14-a348a3fbf1f7@googlegroups.com> NNTP-Posting-Host: NIM2IeSPVd0kE3mU1mieXw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; 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:32678 On 9/24/2015 10:51 PM, Arne Vajhøj wrote: > On 9/24/2015 10:35 PM, Jerry Stuckle wrote: >> On 9/24/2015 9:58 PM, Arne Vajhøj wrote: >>> On 9/24/2015 7:55 PM, Jerry Stuckle wrote: >>>> Not a compiler as known outside of the Java world. It only creates >>>> bytecode, not an executable file. >>> >>> Similar to: >>> >>> C# compiler that compiles C# code to MSIL byte code >>> UCSD Pascal compiler that compiles Pascal code to p-code byte code >>> Hip Hop compiler that compiles PHP to Hip Hop byte code >>> >>> Calling something that compiles to byte code is not a Java world >>> thing - it is quite common - and have been used many years >>> before Java was invented. >>> >> >> Actually, C# can be compiled to machine code. It just needs the .NET >> framework installed, also. >> >> But if you understood C#, you wouldn't make such a stoopid claim. > > The C# compiler always compile to MSIL byte code. > > Which you can easily verify by running ILDASM on the > output. Or one can read the C# specification. Let me make a few quotes: ... When C# programs are compiled, they are physically packaged into assemblies. Assemblies typically have the file extension .exe or .dll, depending on whether they implement applications or libraries. ... Assemblies contain executable code in the form of Intermediate Language (IL) instructions, and symbolic information in the form of metadata. Before it is executed, the IL code in an assembly is automatically converted to processor-specific code by the Just-In-Time (JIT) compiler of .NET Common Language Runtime. ... You like to talk about your many years of programming experience - did those include such exotic activities as reading specifications to understand how things are supposed to work? Arne