Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!aramis.rutgers.edu!atanasoff.rutgers.edu!lou
From: lou@cs.rutgers.edu (lou)
Newsgroups: comp.lang.lisp
Subject: Re: Allegro Lisp <-> Lucid Lisp
Message-ID: <LOU.90Oct8174202@atanasoff.rutgers.edu>
Date: 8 Oct 90 21:42:02 GMT
References: <2845@cernvax.UUCP>
Sender: lou@atanasoff.rutgers.edu
Reply-To: lou@cs.rutgers.edu
Organization: Computer Science Dept., Rutgers University, New Brunswick, NJ
	08903
Lines: 17
In-reply-to: fuchsj@cernvax.UUCP's message of 8 Oct 90 16:34:58 GMT

In article <2845@cernvax.UUCP> fuchsj@cernvax.UUCP (joachim fuchs) writes:

   The problem now is, if anybody already ported applications from Allegro
   Lisp to Lucid Lisp, and if (s)he has encountered any problems of
   compatibility. I know - both of them are supposed to be CommonLisp, but you
   never know... :-)

I have ported small pieces of code (a few pages) from Allegro to
Lucid.  As far as I can tell, if the code to be ported adheres to
standard Common Lisp, porting is trivial.  If it uses non-standardized
extensions (e.g. multiple processes, foreign function calls, etc.) then
porting is harder.  
--
					Lou Steinberg

uucp:   {pretty much any major site}!rutgers!aramis.rutgers.edu!lou 
internet:   lou@cs.rutgers.edu