home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!att-out!rutgers!newsserver.jvnc.net!darwin.sura.net!haven.umd.edu!umd5!umd5.umd.edu!anderson
- From: anderson@sapir.cog.jhu.edu (Stephen Anderson)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: C++ & LISP
- Message-ID: <ANDERSON.93Jan27074214@sapir.cog.jhu.edu>
- Date: 27 Jan 93 12:42:14 GMT
- References: <1k1e30INNnuj@phakt.usc.edu> <1k5oblINNqq6@pith.uoregon.edu>
- Sender: news@umd5.umd.edu
- Distribution: na
- Organization: Dept. of Cognitive Science, The Johns Hopkins University
- Lines: 27
- In-reply-to: bjorn@darmok.uoregon.edu's message of 27 Jan 93 10:32:21 GMT
-
- >>>>> On 27 Jan 93 10:32:21 GMT, bjorn@darmok.uoregon.edu (Bjorn S.
- Fjeld Pettersen) said:
-
- Bjorn> In article <1k1e30INNnuj@phakt.usc.edu>
- Bjorn> thartman@phakt.usc.edu (Tye) writes:
- [C++ discussion deleted]
- >
- > Also, the school is using Lucid Common Lisp/SPARC 4.1 for Lisp
- > development. Is this compatible w/ the Allegro Common Lisp on the
- > NeXT?
-
- Bjorn> Mostly. You should probably compile your ACL as
- Bjorn> case-insensitive, upper-case preferred -- although this
- Bjorn> will preempt any attempt at using ACL with obj-c, IB
- Bjorn> etc. etc.
-
- A correction here: the most recent version of ACL for the NeXT is
- still 3.1.20. This is compatible with the corresponding version on
- Suns, and largely similar to Lucid CL of the same vintage - but
- different in important ways from Lucid (and Allegro) CL 4.x. The main
- difference is that both Lucid and Allegro include (slightly different
- versions of) CLOS in their 4.x implementations. Franz has apparently
- all but finished ACL 4.1 for NeXT, but hasn't seen fit to release it
- yet :-( Until they do, case sensititvity may be the least of your
- problems in porting Sun CL code to the NeXT.
-
- --Steve Anderson
-