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/05 Message-ID: <01bc4155$221728e0$2dfb82c1@xhv46.dial.pipex.com>#1/1 X-Deja-AN: 230784108 References: <5hrkhkINN9ip@snoopy.cis.ohio-state.edu> Organization: UUNet PIPEX server (post doesn't reflect views of UUNet PIPEX) Newsgroups: comp.lang.ada Date: 1997-04-05T00:00:00+00:00 List-Id: Robert A Duff wrote in article ... > In article <5hrkhkINN9ip@snoopy.cis.ohio-state.edu>, > david scott gibson wrote: > >Hi. Could someone summarize the advantages and disadvantages of > >having an Ada compiler that when compiling generic units generates > >code that may be shared by multiple instances? ... > > Well, you pretty much listed the trade-offs. [snip] Don't get confused between 'thunking' and mere indirect jumping/calling. A thunk is where a direct jump/call vector is replaced at runtime (and is thus a one-time thing per execution). I think what you are suggesting is just passing in jump/call vectors, which would be jumped/called to by an indirect jump/call instruction. The vectors could change (by being passed in as hidden parameters) for each instantiation. Nick.