From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,3ef3e78eacf6f938 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!feeder.news-service.com!188.40.43.213.MISMATCH!feeder.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Warren Newsgroups: comp.lang.ada Subject: Re: Interpreted vs. Compiled Date: Mon, 29 Mar 2010 20:51:45 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <7a0c7a19-5d83-4cc6-be68-95ebf41533e7@t23g2000yqt.googlegroups.com> <3b3f991b-8fcd-435c-83f6-e1a1a5e8f6ed@a31g2000prd.googlegroups.com> <87k4sunb9u.fsf_-_@ludovic-brenta.org> Injection-Date: Mon, 29 Mar 2010 20:51:45 +0000 (UTC) Injection-Info: news.eternal-september.org; logging-data="14367"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18pHcLy59pbgKMRq65yYbMMN5zEOcfvGyA=" User-Agent: Xnews/5.04.25 X-Face: &6@]C2>ZS=NM|HE-^zWuryN#Z/2_.s9E|G&~DRi|sav9{E}XQJb*\_>=a5"q]\%A;5}LKP][1mA{gZ,Q!j Cancel-Lock: sha1:QX1E3GYeYgSXWciQu+duRMo1Atk= Xref: g2news2.google.com comp.lang.ada:10775 Date: 2010-03-29T20:51:45+00:00 List-Id: Ludovic Brenta expounded in news:87k4sunb9u.fsf_-_@ludovic-brenta.org: > I do not think any language can be said to be "interpreted" or > "compiled". Instead, any *implementation* of any language can be > "interpreted", "compiled" or something in between. It is almost a > continuum. Under Unix, it is generally accepted that if a 3rd-party (not o/s and not so-called executable) process is required, it is known as the "interpreter". Linux for example used to (probably still does) have the ability to register the "interpreter". This was done with the JVM. Once the JVM was registered, you could launch the byte-code as if it were a native executable-- which is obviously slight-of-hand, since there is the necessary invoking of the "interpreter" as well (it is not purely the o/s being used). Now I only mention "this" particular view (as before) of an interpreter for the very simple utilitarian reason that once you realize that an interpreting "middleman" is involved, it is very obvious (i.e. not surprising) that it runs less efficiently than other native code options. Any other concept of "interpreter" in this discussion of performance is less interesting in this context. BTW, emulation leads to the same conclusion as an interpreter, since it too is "interpreting", even if one doesn't usually call it that. > Interpreted, stricto sensu, means that the interpreter reads the > sources of the program as written by the human programmer. I should probably shutup, but you do know that many of "those" interpreters also use an intermediate code in memory. So just because they don't store it in a file that way, doesn't make them any more special IMO. > You get the drift. Yep. Yep. Warren