Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!das-news.harvard.edu!news2.near.net!MathWorks.Com!europa.eng.gtefsd.com!library.ucla.edu!ihnp4.ucsd.edu!ames!pacbell.com!amdahl!netcomsv!ix.netcom.com!netcom.com!ddyer
From: ddyer@netcom.com (Dave Dyer)
Subject: Re: Porting out of Lucid to better available Lisps:
Message-ID: <ddyerCxDD2J.Cnn@netcom.com>
Reply-To: ddyer@netcom.com
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
X-Newsreader: TIN [version 1.2 PL1]
References: <RAMAN.94Oct6175510@arctic.crl.dec.com>
Date: Sat, 8 Oct 1994 19:35:07 GMT
Lines: 14

	...
    : My question: What are the issues involved in porting from Lucid to CMU Common
    : Lisp?

    : My code is 99.9% CLTL1+ compliant, and I rely on Lucid's run-program for
    : interfacing with things outside the lisp world.

In that case, you shouldn't have any great difficulty.  I've
personally worked with even larger systems that could be compiled
under lucid, franz, or harlequin lisp.

Even in the .1% of non-cl code, lucid, franz, and harlequin tend to have
very similar nonstandard extensions which cover the same ground, albeit
in slightly incompatible ways.
