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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,37680a99b5e22b2b X-Google-Attributes: gid103376,public From: "Nick Roberts" Subject: Re: Shared Generic Instance Code Date: 1997/04/06 Message-ID: <01bc42b0$18bc4440$90f482c1@xhv46.dial.pipex.com>#1/1 X-Deja-AN: 231110680 References: <5hrkhkINN9ip@snoopy.cis.ohio-state.edu> <1997Apr1.201631.28634@ocsystems.com> <5i23k6$hkq@mulga.cs.mu.OZ.AU> <3346F7E8.78E6@bix.com> Organization: UUNet PIPEX server (post doesn't reflect views of UUNet PIPEX) Newsgroups: comp.lang.ada Date: 1997-04-06T00:00:00+00:00 List-Id: Tom Moran wrote in article <3346F7E8.78E6@bix.com>... > > design choice that favors efficiency over space > Though I haven't done a lot of timing studies, I have the distinct > impression that big generics can *drastically* slow down compilation > (Gnat 3.04a NT/95). I presume the macro is essentially expanded and > recompiled each time it's instantiated? > I think he means efficiency (i.e. greater executional speed) of the output executable, not of the compilation process itself. Nick.