Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!dsl.pitt.edu!pitt!cs.pitt.edu!sylvester!field
From: field@sylvester.cs.pitt.edu (Gus)
Newsgroups: comp.lang.lisp
Subject: Re: Porting KCL C code
Keywords: KCL Lisp C port
Message-ID: <1990Feb14.163819.13849@cs.pitt.edu>
Date: 14 Feb 90 16:38:19 GMT
References: <7993@lindy.Stanford.EDU> <1739@skye.ed.ac.uk>
Sender: news@cs.pitt.edu
Reply-To: field@sylvester.cs.pitt.edu (Brian Field)
Organization: Computer Science Dept., Univ. of Pittsburgh
Lines: 31

In article <1739@skye.ed.ac.uk> jeff@aiai.UUCP (Jeff Dalton) writes:
>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?
>
>I'm not quite sure what you mean.  It can be compiled by the C
>compiler.  But it's a bunch of procedure definitions, not a complete
>program.
>

>The intermediate code is fairly portable, so it will probably compile.
>
>>Or does the code require the KCL environment?
>
>It calls procedures that are part of the KCL system and it expects
>to be loaded into a running KCL.  It would not be too hard to hard
>to link it together with the files that make up KCL instead.  If you
>wanted to convert KCL into a library and have the compiler compile
>files that had to be linked with that library, it would probably be
>possible to do that.  But that isn't how it works now.
>

Has anyone done this?  I would like to be able to run compiled lisp
code outside of the KCL environment.  Any info appreciated.

Brian
-----
field@cs.pitt.edu