Path: utzoo!utgpu!water!watmath!dalcs!hemphill
From: hemphill@dalcs.UUCP (Gavin Hemphill)
Newsgroups: comp.sys.mac
Subject: Re: Status of Allegro Common Lisp?
Message-ID: <2756@dalcs.UUCP>
Date: 5 Jan 88 00:21:01 GMT
References: <2169@mhuxt.UUCP>
Reply-To: hemphill@dalcs.UUCP (Gavin Hemphill)
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Lines: 21

In article <2169@mhuxt.UUCP> evans@mhuxt.UUCP (Sukie Crandall) writes:
>
>Has anyone used Allegro Common Lisp (from Coral Software)? The review in Byte
>(current issue) made it look promising. Specifically is there a release >
>1.0 and what are its features? What is the status of CLOS for Allegro CL?
>What kind of upgrade policy do they have (eg. should I buy now and trust
>them for inexpensive upgrades or should I wait for something a little more
>finished)?
>
	I've been using the Allegro Common Lisp since it first came out, and
the simplest answer is that it is a FULL Common Lisp which works very well
on the Mac (I'd recommend at least 2.5 Mbytes of RAM though).  I'm currently
running CLOS (The Dec 8th version from the coral directory at parcvax) and
have had no problems to speak of.  The current version is 1.1, which provided
a few minor bug fixes and Multifinder awareness.  Its great being able to do
software development at home, then simply transfer the code to the Symbolics
at work and have it run, the only difference being speed.
	As for specific features, I particularly like the logical pathname
scheme and the ease of access to the toolbox routines -- now if we only had
the stand alone compiler available (which is supposed to happen sometime
this year) I'd be really happy.