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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fcc2d88d867060e8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-12-20 12:13:05 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.mathworks.com!wn14feed!worldnet.att.net!207.115.63.142!prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr23.news.prodigy.com.POSTED!7db1df25!not-for-mail From: lifetime n00b User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031014 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: load and use a ".o" file? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <132Fb.3462$I02.2996@newssvr23.news.prodigy.com> NNTP-Posting-Host: 66.25.226.7 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr23.news.prodigy.com 1071951165 ST000 66.25.226.7 (Sat, 20 Dec 2003 15:12:45 EST) NNTP-Posting-Date: Sat, 20 Dec 2003 15:12:45 EST Organization: SBC http://yahoo.sbc.com X-UserInfo1: FKPO@MC@OXUWRR@XABIXOFXBWR\HPCTL@XT^OBPLAH[\RSAANVUEAE[YETZPIWWI[FCIZA^NBFXZ_D[BFNTCNVPDTNTKHWXKB@X^B_OCJLPZ@ET_O[G\XSG@E\G[ZKVLBL^CJINM@I_KVIOR\T_M_AW_M[_BWU_HFA_]@A_A^SGFAUDE_DFTMQPFWVW[QPJN Date: Sat, 20 Dec 2003 20:12:45 GMT Xref: archiver1.google.com comp.lang.ada:3641 Date: 2003-12-20T20:12:45+00:00 List-Id: Stephen Leake wrote: > .dll and .so files are designed to do _precisely_ what you are trying > to do; they are the most efficient solution! Well, not _precisely_, since a typical program using the .dll or .so files needs to know about those files when it is compiled itself, right? Maybe I wasn't clear on exactly what I need to do. The program that needs to load and use the object file is *already running* before the object file is compiled. This "main program" has no prior information about the data or routines which may be in the object file it is being told to load. The "main program" operates much like a command prompt, and when (compile-file "hithere") is typed at the prompt, gnat will be called to compile an object file. Then when (load "hithere") is typed at the prompt, the object file is loaded and the data and/or functions in "hithere" are now available to the main program. Some additional information may have to be included in a supporting file produced at the same time the object file is produced, and this supporting file would be loaded when the object file is loaded. That's the idea anyway. But I'm having a difficult time trying to figure out how to accomplish this seemingly straightforward task.