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,ff82986c79efd148
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Q: inlining
Date: 1996/06/20
Message-ID: <dewar.835244567@schonberg>#1/1
X-Deja-AN: 161449763
references: <JSA.96Jun18121906@organon.com>
 <Dt9Dn2.7vF.0.-s@inmet.camb.inmet.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-20T00:00:00+00:00
List-Id: <comp.lang.ada>


Tucker said

"Yes, ObjectAda/AdaMagic does inlining across compilation units.
It requires that the source file containing the body already be
"registered" in the program library when you compile a call to the
subprogram."

Tuck, you might want to emphasize that this registration has nothing
to do with compilation, so, as is the case with GNAT, Ada Magic allows
completely general inlining without having to worry about the order
in which things are compiled (at least I assume this is the case!)

Note that the registration in Ada Magic is essentially similar to placing
Source_File_Name pragmas in gnat.adc in GNAT, the only difference is that
in GNAT you can if you like avoid this step by using the default file
names (which is what most, but not all, GNAT users prefer to do).