From ... From: Erik Naggum Subject: Re: Lisp & C Date: 2000/10/24 Message-ID: <3181389901300909@naggum.net>#1/1 X-Deja-AN: 685281052 References: <39F597AE.F753BF3C@utbm.fr> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 972403059 4981 195.0.192.66 (24 Oct 2000 15:57:39 GMT) Organization: Naggum Software; vox: +47 800 35477; gsm: +47 93 256 360; fax: +47 93 270 868; http://naggum.no; http://naggum.net User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 Mime-Version: 1.0 NNTP-Posting-Date: 24 Oct 2000 15:57:39 GMT Newsgroups: comp.lang.lisp * Matias GUIJARRO | I would like to know how to merge Lisp & C in a same program, I mean | for example writting the interface in C and AI things in Lisp. If you seperate the functionality that well, you might benefit from not marrying (merging) the two together, but rather to use a looser coupling through an intermediate layer. Several options exists for this, including CORBA, RPC, and rolling your own protocol, using socket communication. You may find this easier on your design than to do extensive amounts of work in C-land while running a Lisp system, mostly because calls to C are usually assumed to be short special service calls. If you are dealing with a more server-like approach to the AI stuff while the C subsystem is doing the (user) interface, you will probably benefit from a very loose coupling. Unfortunately, protocol design and implementation in C is much harder than in Lisp, so C programmers do not naturally gravitate towards those kinds of designs, but prefer expensive solutions as long as they are in some sort of library. #:Erik -- I agree with everything you say, but I would attack to death your right to say it. -- Tom Stoppard