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,37680a99b5e22b2b X-Google-Attributes: gid103376,public From: jvl@ocsystems.com (Joel VanLaven) Subject: Re: Shared Generic Instance Code Date: 1997/04/01 Message-ID: <1997Apr1.201631.28634@ocsystems.com>#1/1 X-Deja-AN: 229947407 References: <5hrkhkINN9ip@snoopy.cis.ohio-state.edu> Organization: OC Systems, Inc. Newsgroups: comp.lang.ada Date: 1997-04-01T00:00:00+00:00 List-Id: david scott gibson (dgibson@snoopy.cis.ohio-state.edu) 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? On the negative side, : I suspect that it increases compiler complexity and could result in : slower executables. On the positive side, it could reduce the size of : executables and perhaps reduce the amount of recompilation in system : generation. Are there other issues such as interaction with other : Ada language features or the presumed utility of code sharing, that : make one approach more attractive than the other? : Dave Well, I'll not summarize but make one point. Environments that use code sharing may have an easier (more human intuitive) time with with source level debugging. In order to set a breakpoint generic unit n a multi- instance environment one must know which instance. In a code-sharing situation the code being debugged is more intuitively linked to the source code. Such things can certainly be overcome, but will probably add complexity to the compiler and/or debugger (that was supposed to be simpler). -- -- Joel VanLaven