Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!nagler@seismo.CSS.GOV@olsen.UUCP From: nagler@seismo.CSS.GOV@olsen.UUCP (Robert Nagler) Newsgroups: comp.lang.modula2 Subject: Standards and Terms Message-ID: <8612141239.AA02528@olsen.uucp> Date: Tue, 16-Dec-86 02:07:54 EST Article-I.D.: olsen.8612141239.AA02528 Posted: Tue Dec 16 02:07:54 1986 Date-Received: Wed, 17-Dec-86 04:52:46 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 14 There were a few messages in which my use of the term "compiler" was misunderstood. The word "compiler" is compiler, linker, loader, etc. I make no distinction. In the future, I probably should refer to the group as a "language processor". To make my previous point clearer: a language processor can inline anything, that is, it can remove all procedure calls from a single executed entity. In the case of dynamic linking, this may be a little more difficult and time consuming. Since most linkers are static (why? why? why?), the previous argument is valid. Sorry for the confusion, I will try to be more clear in the future. Rob Nagler