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,a02ecdd4cb0f0996 X-Google-Attributes: gid103376,public From: Gautier Subject: Re: Pragma Inline and its Effects of Compilation Dependencies. Date: 2000/03/21 Message-ID: <38D7F4D8.1AE44625@maths.unine.ch>#1/1 X-Deja-AN: 600566402 Content-Transfer-Encoding: 7bit References: <8b64ul$jov$1@inputplus.demon.co.uk> <8b8gen$mko$1@nnrp1.deja.com> <38D7CABA.A73F88C6@cadence.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: 21 Mar 2000 22:15:38 +0100, mac13-32.unine.ch Organization: Maths - Uni =?iso-8859-1?Q?Neuch=E2tel?= MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-03-21T00:00:00+00:00 List-Id: > > One of the big advantages of the source based model used first > > by GNAT, and later by some (but not all) other Ada 95 compilers > > is that inlining can be done accurately. Paul Graham wrote: > Makes you wonder why the library-based method of compilation was used in > the first place. Perhaps the intent was to save compilation time by not > recompiling package sources each time they are USEd in another unit. This feature doesn't force the library model in the classical Ada83 way. E.g. Turbo Pascal and successors/clones. Or maybe the "other" Ada95 compilers ? And it doesn't prevent accurate inlining if compiled specification holds rich enough information (e.g. from where to pick the procedure to inline in the source of package body, or some representation of it ?) ______________________________________________________ Gautier -- http://members.xoom.com/gdemont/gsoft.htm