Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!ukc!edcastle!aiai!jeff
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Newsgroups: comp.lang.lisp
Subject: Re: Porting KCL C code
Keywords: KCL Lisp C port
Message-ID: <1739@skye.ed.ac.uk>
Date: 12 Feb 90 21:05:39 GMT
References: <7993@lindy.Stanford.EDU>
Reply-To: jeff@aiai.UUCP (Jeff Dalton)
Organization: AIAI, University of Edinburgh, Scotland
Lines: 30

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.

>Can the intermediate C code be compiled on another machine,
>say a 386 machine, and work?

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.

I would be surprised if any Lisp -> C generated C code that didn't
even have to be linked with a library of procedures for manipulating
Lisp data structures.

-- Jeff