Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!ucbvax!dewey.soe.berkeley.edu!mkent
From: mkent@dewey.soe.berkeley.edu (Marty Kent)
Newsgroups: comp.lang.lisp
Subject: Re: (actually none) Some problems with Coral Allegro CL
Keywords: lisp,coral
Message-ID: <28417@ucbvax.BERKELEY.EDU>
Date: 16 Mar 89 09:17:21 GMT
References: <424@soi.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: mkent@dewey.soe.berkeley.edu.UUCP (Marty Kent)
Organization: School of Education, UC-Berkeley
Lines: 21

I just want to get a bit more realistic a tone in this thread.  While I
do the majority of my programming nowadays with Allegro on a Mac II, and I
think it's a quite decent system, it's by no means free from bugs.  Parts
of the low-level system interface are a bit screwed up (Allegro throws up
on pointers into ROM, for instance most pointers returned by calling
GetTrapAddress cause errors), the inspector is subject to cause system
divide-by-zero errors on a fairly regular basis, there are problems with
the scrolling capabilities of table-dialog-items, etc. etc. 

I don't mean to run the system down; I use it on a daily basis and I
certainly don't regret making the commitment to base several large
development efforts in it.  But there are more than enough holes (the
above list is just off the top of my head, by no means exhaustive) in the
system to "keep life interesting..."


Marty Kent  	Sixth Sense Research and Development
		415/642 0288	415/548 9129
		MKent@dewey.soe.berkeley.edu
		{uwvax, decvax, inhp4}!ucbvax!mkent%dewey.soe.berkeley.edu
Kent's heuristic: Look for it first where you'd most like to find it.