Re: The compilation approach in modern languages

"Ganny" <sgganesh@gmail.com>
12 Feb 2005 17:46:20 -0500

          From comp.compilers

Related articles
The compilation approach in modern languages sgganesh@gmail.com (Ganny) (2005-02-11)
Re: The compilation approach in modern languages rbates@southwind.net (Rodney M. Bates) (2005-02-12)
Re: The compilation approach in modern languages sgganesh@gmail.com (Ganny) (2005-02-12)
Re: The compilation approach in modern languages bobduff@shell01.TheWorld.com (Robert A Duff) (2005-02-13)
Re: The compilation approach in modern languages cartazio@gmail.com (Carter Schonwald) (2005-02-13)
Re: The compilation approach in modern languages dot@dotat.at (Tony Finch) (2005-02-13)
Re: The compilation approach in modern languages gah@ugcs.caltech.edu (glen herrmannsfeldt) (2005-02-13)
Re: The compilation approach in modern languages nmm1@cus.cam.ac.uk (2005-02-16)
Re: The compilation approach in modern languages boldyrev@cgitftp.uiggm.nsc.ru (Ivan Boldyrev) (2005-02-16)
[14 later articles]
| List of all articles for this month |

From: "Ganny" <sgganesh@gmail.com>
Newsgroups: comp.compilers
Date: 12 Feb 2005 17:46:20 -0500
Organization: http://groups.google.com
References: 05-02-053 05-02-056
Keywords: design, Java

>>It is a common misconception that certain languages are "interpreted"


>>and others are "compiled" In fact, the distinction between compiled
>>and interpreted (and hybrids) is not a property of the language, but
>>only of the implementation.


Also, it is true that languages are designed with particular
implementation approaches in mind. It would be a misconception to think
that C was designed for interpreation approach in mind and Java was
designed with native compilation in mind.


-Ganesh
[I think you'll find that Java was designed to be compiled into
interpreted byte codes, native code via JIT from byte codes, or
directly to native code. C was certainly designed with native code in
mind. =John]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.