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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,97482af7429a6a62 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,97482af7429a6a62 X-Google-Attributes: gid103376,public X-Google-Thread: 10d15b,97482af7429a6a62 X-Google-Attributes: gid10d15b,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Language Efficiency Date: 1995/04/04 Message-ID: <1995Apr4.174002.9577@eisner.decus.org>#1/1 X-Deja-AN: 100814208 references: <3lmt64$stt@dplanet.p2k.cbis.com> <3lrrqk$kbj@usenet.INS.CWRU.Edu> organization: DECUServe newsgroups: comp.lang.c++,comp.lang.ada,comp.lang.cobol Date: 1995-04-04T00:00:00+00:00 List-Id: In article <3lrrqk$kbj@usenet.INS.CWRU.Edu>, bb206@cleveland.Freenet.Edu (Harold P Zbiegien) writes: > > In a previous article, robertb@cbis.com (Robert C. Bethel) says: > >>Anyone know of research papers that deal with the subject >>of language efficiency? By efficiency I mean the quality >>of machine binaries (code space, execution time, etc.) >>given an identical program coded in several languages. >> >>Thanks >>-- >>Robert.Bethel@CBIS.Com >> > Shouldn't this be labeled "compiler efficiency" There may not be anything > inherent between the efficiency of one language and another, but there sure > is differences between the generated code coming out of compilers. > > Harold > American Greetings Corp. Although efficiency of compilers is the controlling issue for most environments (due to the low state of optimization for most widely used compilers), language efficiency is a separate issue which would be of interest if compilers were not masking the effects. One opinion is that "higher level" languages with strong type checking give the compiler a better chance to understand what the programmer really intended and optimize accordingly. Of course this also depends on the programmer having coded what was really intended. Finally, let me note that the two specific examples given by Robert, "code space" and "execution time" are often at odds with each other, so a robust compiler will let the user indicate a preference. Larry Kilgallen