Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!newsfeed.internetmci.com!EU.net!sun4nl!aie.nl!news
From: geert@michelv.aie.nl (Geert-Jan van Opdorp)
Subject: LispWorks or Allegro?
Sender: news@aie.nl (Usenet News)
Message-ID: <GEERT.96Jan19160313@michelv.aie.nl>
Date: Fri, 19 Jan 1996 15:03:12 GMT
Lines: 40
X-Nntp-Posting-Host: michelv.aie.nl
Organization: AI Engineering BV, Amsterdam, Netherlands

Hi,
We want to buy a Cltl2 compliant Common Lisp to further develop
(on Solaris) our (rather big) system that was runs now on Lucid.
We are using an object system that we implemented ourselves in
lisp, but we want to port it to Clos. So far our impression is
that LispWorks and Allegro are good choices, but we would like
to hear some comments from people who used these products.

Important issues for us:

Performance of compiled code. How fast/slow is clos code
on these platforms. Can we find benchmarking results
somewhere?

Full Cltl2 compliancy

Good development environment

Meta object protocol implemented

Portability to a WindowsNT platform: What are the
experiences with the LispWorks Transducer? 
Is the non-standard stuff like the foreign 
function interface the same for the
Unix and WindowsNT versions of Allegro?


If you have experience with either Allegro or LispWorks,
I would appreciate your comments on any of the above 
points very much.

Thanks,

Geert-Jan.

-- 
Geert-Jan van Opdorp
AI-Engineering
Amsterdam, The Netherlands
geert@aie.nl
