fuchsj@cernvax.UUCP (joachim fuchs) (10/08/90)
Hi netters, I've got the following problem and would like to know if anybody else out there has some more detailed information: We are developping an expert system for the diagnosis of a large system in the physics domain (particle accelerators). For several reasons (I do not want to quote them all) we are obliged to switch to a SUN 3/50 for our application. We are using KEE as shell, which requires apparently Lucid Lisp to work properly. On the other hand we will get a rather large software package, written also in CommonLisp, but this time for Allegro Lisp. 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... :-) Please email answers BITNET: fuchsj@cernvm.cern.ch or fuchsj@cernvax.cern.ch Thanks a lot in advance Joachim Fuchs CERN/Div. PS 1211 Geneva 23
lou@cs.rutgers.edu (lou) (10/09/90)
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