Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!mcnc!ecsvax!dgary
From: dgary@ecsvax.UUCP (D Gary Grady)
Newsgroups: net.lang.c
Subject: Re: C vs. FORTRAN (was: What should be added to C)
Message-ID: <1622@ecsvax.UUCP>
Date: Wed, 28-May-86 11:39:27 EDT
Article-I.D.: ecsvax.1622
Posted: Wed May 28 11:39:27 1986
Date-Received: Thu, 29-May-86 07:34:23 EDT
References: <1594@ecsvax.UUCP> <853@bentley.UUCP> <1621@ecsvax.UUCP>
Reply-To: dgary@ecsvax.UUCP (D Gary Grady)
Organization: Duke U Comp Ctr
Lines: 21
Summary: What "inline" means

In my last two postings I used the term "in-line" with respect to
FORTRAN functions and it occurs to me a quick explanation might be in
order.  An "in-line function" is one that a compiler expands into
in-line machine language as opposed to a procedure call.  Where speed
is of the essence (as it often is in FORTRAN programs), this can make a
significant difference on some machines.  FORTRAN programmers have to
worry about a given function being "in-line" or "out-of-line" if they
want to create one of the same name.  Thus in-line function names
effectively constitute the only "reserved words" in FORTRAN.

In addition to the in-line functions, FORTRAN has many other "built-in"
functions, that is, those that are a defined part of the language.
This means that these scientific function names are identical over all
implementations of the language, a very important consideration in
writing huge programs that will be used at many sites on different
equipment.
-- 
D Gary Grady
Duke U Comp Center, Durham, NC  27706
(919) 684-3695
USENET:  {seismo,decvax,ihnp4,akgua,etc.}!mcnc!ecsvax!dgary