Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!quiche!utility
From: utility@quiche.cs.mcgill.ca (Ronald BODKIN)
Newsgroups: comp.lang.lisp
Subject: Re: Porting KCL C code
Keywords: KCL Lisp C port
Message-ID: <2186@quiche.cs.mcgill.ca>
Date: 13 Feb 90 01:36:32 GMT
References: <7993@lindy.Stanford.EDU>
Reply-To: utility@quiche.cs.mcgill.ca (Ronald BODKIN)
Organization: SOCS, McGill University, Montreal, Canada
Lines: 15

In article <7993@lindy.Stanford.EDU> giant@lindy.Stanford.EDU (Buc Richards) writes:
>
>KCL (Kyoto Common Lisp) translates programs from Lisp to C and then
>compiles the C to generate compiled programs.  Is the C code generated
>complete?  Can the intermediate C code be compiled on another machine,
>say a 386 machine, and work?  Or does the code require the KCL
>environment?
	The code will compile, but you would need to at least emulate
a number of fairly fundamental environmental assumptions (e.g.
some lisp stacks, calling protocols, some functions) so essentially
you do need the environment.  It would be neat to have a LISP which
could create complete, independent modules, but due to the way people
write lisp it would probably still have to package in alot of LISP 
functions...
		Ron