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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a4cc6fdc99d3fe2a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-31 12:08:19 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!bos-service2.ext.raytheon.com.POSTED!not-for-mail Message-ID: <3B16969B.1C8AFD20@ftw.rsc.raytheon.com> From: Wes Groleau X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en,es,fr,pt MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: package body functionality References: <9eoeiv$h8$1@eol.dd.chalmers.se> <9f14b8$r4v$1@nh.pace.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 31 May 2001 14:08:11 -0500 NNTP-Posting-Host: 151.168.144.162 X-Complaints-To: news@ext.ray.com X-Trace: bos-service2.ext.raytheon.com 991336094 151.168.144.162 (Thu, 31 May 2001 15:08:14 EDT) NNTP-Posting-Date: Thu, 31 May 2001 15:08:14 EDT Organization: Raytheon Company Xref: archiver1.google.com comp.lang.ada:7949 Date: 2001-05-31T14:08:11-05:00 List-Id: > >Possible exception: If the package is a shared library or in a distributed > >environment. I'm not sure what the language rules are, but I'd suspect that > >a DLL would not re-elaborate every time another program started up and > >called for its services. Maybe under some conditions (separate data spaces) > > My understanding is that DLL's keep a count of how many programs are using them, > and get automagicly unloaded when the count goes down to 0. You'd want it to > elaborate once for the first call that loads it in, then not again until the > next call after it unloads. There are many things a package in a DLL or shared lib might do during elaboration that would require re-elaboration for each client. Just for a few: Create a log file. Initialize a random number generator. Read the process ID. Note the time we started running. Doesn't seem practical for a compiler/linker to foresee ALL the possibilities and optionally skip elaboration. -- Wes Groleau http://freepages.rootsweb.com/~wgroleau