Received: from scaup.cl.cam.ac.uk by Steve.CL.Cam.AC.UK with SMTP/TCP/IP over Ethernet id a013411; 9 Dec 88 10:37 GMT Via: uk.ac.ucl.cs.nss; 9 Dec 88 10:31 GMT (UK.AC.Cam.Cl.scaup) Received: from clover.ucdavis.edu by NSS.Cs.Ucl.AC.UK via Satnet with SMTP id aa03420; 9 Dec 88 9:19 GMT Received: from IU.AI.SRI.COM by clover.ucdavis.edu (5.59/UCD.EECS.1.1) id AA07077; Fri, 9 Dec 88 01:24:39 PST Received: from drakes.ai.sri.com by IU.AI.SRI.COM via SMTP with TCP; Fri, 9 Dec 88 01:23:07-PST Received: from cam.sri.com (cambridge) by drakes.ai.sri.com (3.2/4.16) id AA00815 for info-hol@clover.ucdavis.edu; Fri, 9 Dec 88 01:23:03 PST Received: from gwyndir.cam.sri.com by cam.sri.com (3.2/4.16) id AA14955 for info-hol@clover.ucdavis.edu; Fri, 9 Dec 88 09:21:47 GMT Received: by gwyndir.cam.sri.com (3.2/4.16) id AA00760 for info-hol@clover.ucdavis.edu; Fri, 9 Dec 88 09:21:43 GMT Date: Fri, 9 Dec 88 9:06 GMT From: Mike Gordon To: info-hol@edu.ucdavis.clover Subject: SML vs Common Lisp Message-Id: Sender: mjcg Status: RO I think any port to Common Lisp should still preserve the Franz Lisp version. I would not expect that we would switch to Common Lisp at Cambridge as I gather 12mbytes SUNs are a minimal platform for running Common Lisp. The hope would be that, via suitable macros and conditional compilation, the system would build in both Lisps (just as it now builds in MacLisp and Zeta-Lisp as well as Franz). I would certainly hope the system would build in all Common Lisps! ICL have also suggested using the RAL Lisp implementation of SML as a first step towards HOL in SML. The result might be rather slow, but it could be made compatible with future fast implementations using new Jersey ML or Poly/ML. I have not looked at the RAL LCF sources, so I don't know how much work it would be to use them. Mike