Xref: utzoo comp.lang.c:39480 comp.lang.lisp:4922 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!ariel.unm.edu!nmsu!opus!ted From: ted@nmsu.edu (Ted Dunning) Newsgroups: comp.lang.c,comp.lang.lisp Subject: Re: Calling LISP from C (QUERY) Message-ID: Date: 22 May 91 22:10:59 GMT References: <1096@redford.UUCP> <1991May22.180731.4991@Think.COM> Sender: news@NMSU.Edu Followup-To: comp.lang.c Organization: Computing Research Lab Lines: 27 In-reply-to: barmar@think.com's message of 22 May 91 18:07:31 GMT In article <1991May22.180731.4991@Think.COM> barmar@think.com (Barry Margolin) writes: In article <1096@redford.UUCP> bill@redford.UUCP (Bill Poitras(X258)) writes: >I am trying to take some common LISP code which has some very complex >algorithms and interface them to C. The specifics: ... What you generally *can* do is load C object files into a running Lisp. it is often simpler to connect a c program an a lisp program with something like a pair of pipes, or a socket. then you can write code which allows the either side to (effectively) call procedures on the other side. this sort of home brew remote procedure is often much more portable between lisps and c programming environments than any foreign function interface. an additional advantage is that the debugging of each side is not disturbed. it is much harder to debug c code when it is loaded into a lisp image. -- if feeling bad is a justification for not living, then living is a justification for feeling good.