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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable 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-30 08:58:48 PST Path: archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!news.level3.com!zeus.visi.com!priapus.visi.com!orange.octanews.net!news.octanews.net!news-out.visi.com!petbe.visi.com!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsoutpeer00.lnd.ops.eu.uu.net!lnewsinpeer00.lnd.ops.eu.uu.net!emea.uu.net!mephistopheles.news.clara.net!news.clara.net!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: load and use a ".o" file? Date: 30 Dec 2003 11:56:43 -0500 Organization: Cuivre, Argent, Or Message-ID: References: <132Fb.3462$I02.2996@newssvr23.news.prodigy.com> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1072803417 34913 80.67.180.195 (30 Dec 2003 16:56:57 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Tue, 30 Dec 2003 16:56:57 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.3 Precedence: list List-Id: Gateway to the comp.lang.ada Usenet newsgroup List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:3951 Date: 2003-12-30T11:56:43-05:00 j-anthony@rcn.com (Jon S. Anthony) writes: > Stephen Leake writes: > > > But I'd still like to understand what the linking process implied by > > (compile 'foo). As far as I can see, it must do the equivalent of > > Windows DLL or Unix so. > > No, this is part of the underlying introspective environment. It is > actually much simpler than the contortions involved in DLL/so type > stuff. It is also fine grained - a function at a time or even a > functions symbol at a time. Well, ok. I don't have a DLL manual handy. Fine-grained would be nice. Maybe sometime I'll find the time to read up on Lisp implementations. I suspect lambda binding, which is very dynamic, actually simplifies the issue of dynamic code loading. > In CL you don't need an explaination of the mechanism unless you are > _implementing_ a Common Lisp. Ok. I'm interested in the implementation details. > For the user, you don't need to do anything other than (compile-file > ...) (load ...) to get all the resources in native compiled form > "linked" in and ready to use. Or for interactive work, just (compile > 'your-foo-here). That's it. A pleasent thing indeed. Right. In VxWorks, you get almost the same convenience, except you have to do the compile on the host, and execute on the target. -- -- Stephe