Xref: utzoo comp.lang.lisp:2829 comp.sys.mac.programmer:12700 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!cambridge.apple.com!alms From: alms@cambridge.apple.com (Andrew L. M. Shalit) Newsgroups: comp.lang.lisp,comp.sys.mac.programmer Subject: MACL Mailing Lists (was: Information Exchange) Message-ID: Date: 23 Feb 90 21:19:29 GMT References: <1532@zipeecs.umich.edu> Sender: news@cambridge.apple.com Distribution: usa Organization: Apple Computer Inc, Cambridge, MA Lines: 36 In-reply-to: arie@dip.eecs.umich.edu's message of 23 Feb 90 03:36:51 GMT In article <1532@zipeecs.umich.edu> arie@dip.eecs.umich.edu (Arie Covrigaru) writes: I am using MACL exclusively and, like on any large Lisp system, sometimes I have problems that are not mine. When I programmed on the Xerox 1100 series Lisp Machines, there was a place where I could exchange information (and still is), public domain hacks, complain about bugs in the system etc. Are there enough people using MACL to form such a group? We're in the process of starting a mailing list for such discussions. The address is: info-macl@cambridge.apple.com If you want to be added to the mailing list, send a request to info-macl-request@cambridge.apple.com As GZ noted, bug reports can be sent to bug-macl@cambridge.apple.com Since I bought Macintosh Allegro Common Lisp from a receptionist at APDA, I have no way to ask her, for example, why the Lisp crashes from time to time without any apparent reason and if the developers are aware of that and are working on fixing it. This and a few other bugs in 1.3.1 have been fixed. In a couple weeks we'll be sending out a free update to everyone who got 1.3.1. :-) Cheers! -andrew shalit alms@cambridge.apple.com