Is Allegro Common Lisp 3.1 broken under NS 3.0?

Article View: comp.sys.next.misc

Article #2270

Back to comp.sys.next.misc Previous Next

#2270

From: Peter Milne
Date: Fri, 28 Aug 1992 06:53

16 lines
1046 bytes

According to Franz, Allegro Common Lisp 3.1 won't run under NeXTstep 3.0,
there is no workaround, and they won't be developing one.

Further questioning revealed they don't actually have NS 3.0 so they
can't have tried ACL 3.1 under it.  It seems that they are mainly interested
in having people pay to upgrade to ACL 4.1 which was due in September but
might be delayed until they get NS 3.0.

The actual version of Allegro Common Lisp I have is 3.1.20.  Can anyone
tell me for sure whether this works under NS 3.0?

I've got my fingers crossed that FrameMaker 2.0d will work under NS 3.0
too.  Anyone know about that?

Thanks
    Peter	(milne@csis.dit.csiro.au)

Technical Details

Message-ID: <1992Aug28.065321.10433@csis.dit.csiro.au>

Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!manuel!csis!pwm

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.misc
Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!manuel!csis!pwm
From: pwm@csis.dit.csiro.au (Peter Milne)
Subject: Is Allegro Common Lisp 3.1 broken under NS 3.0?
Message-ID: <1992Aug28.065321.10433@csis.dit.csiro.au>
Organization: CSIRO Division of Information Technology
Distribution: world 
Date: Fri, 28 Aug 1992 06:53:21 GMT
Lines: 16