Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!nntp.club.cc.cmu.edu!hudson.lm.com!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!pipex!uknet!festival!edcogsci!jeff
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Subject: Re: Lisp->C compilers
Message-ID: <CyrqAJ.Gz2@cogsci.ed.ac.uk>
Sender: usenet@cogsci.ed.ac.uk (C News Software)
Nntp-Posting-Host: bute-alter.aiai.ed.ac.uk
Organization: AIAI, University of Edinburgh, Scotland
References: <poeck-2310942254080001@wi6a65.informatik.uni-wuerzburg.de> <396ukt$gus@tribune.usask.ca>
Date: Sat, 5 Nov 1994 00:20:41 GMT
Lines: 15

In article <396ukt$gus@tribune.usask.ca> srini@cs.usask.ca (P. Srinivas) writes:
>  We have used CLICC to translate a non-trivial application (3-4 K lines)
>written in Common LISP to be able to link with another main module 
>written in C. Though CLICC does not translate full CL, it has a fairly 
>good subset translater. They define CL_0 shihc is translatable subset of
>CL. (mostly omiited things are like EVAL FUNCALL etc). You
>migth want to give it a try, and I think it might work for you.

They really omit *FUNCALL*?  EVAL I can believe, but FUNCALL is
a bit extreme.  If they can't handle FUNCALL, how can they handle
anything (FIND-IF, MAPCAR, REDUCE, etc, etc) that takes functional
arguments?  Do they compile them all in-line and habdle only the
cases that can be dealt with that way?

-- jeff
