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: 103376,8f8cea8602e61aba X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: The Red Language Date: 1997/09/11 Message-ID: #1/1 X-Deja-AN: 271583781 References: <340ED5D8.2DEF6D3@ux4.sp.cs.cmu.edu> <199709051335.PAA25952@basement.replay.com> <34102DF5.36D589F1@ux4.sp.cs.cmu.edu> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-09-11T00:00:00+00:00 List-Id: Art said <> Just because a language definition says XXX does not make it so, if the statement is vacuous. For example, supposed we come across a statement in a language definition that sayys All procedures in this language shall be octagonal. Now we go and look up in the index what octagonal means, and if we don't find a definition, then at best this is a comment with no normative force, and at worst it is rubbish. A statement that certain procedure calls shall be inlined is similarly dubious in the absence of a definition of inlining *at an appropriate level of abstraction* -- a definition that talks about generated code is junk, since you cannot define the notion of generated code in abstract. Remember that a compiler is always allowed to treat a language definition "as-if", which means that any generated code that makes a compiler run the code the same way as some other way is equivalent. Since inlining has, by definition, no semantic effect, it is obvious that semantic rules in the language can neither require it nor proscribe it. As for "we believed him, why not?", the why not is because the claim was on its face unsupportable!