Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!etive!aiai!jeff
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Newsgroups: comp.lang.lisp
Subject: Re: pointers in Lisp
Message-ID: <191@skye.ed.ac.uk>
Date: 16 Feb 89 19:23:18 GMT
References: <1710@cps3xx.UUCP> <33722@tut.cis.ohio-state.edu> <49734@yale-celray.yale.UUCP> <Feb.7.11.41.26.1989.517@lightning.rutgers.edu> <36238@think.UUCP> <624@internal.Apple.COM> <36318@think.UUCP>
Reply-To: jeff@aiai.UUCP (Jeff Dalton)
Organization: AIAI, University of Edinburgh, Scotland
Lines: 21

In article <624@internal.Apple.COM> shebs@Apple.COM (Stanley Todd Shebs)
writes: 
  In article <36238@think.UUCP> barmar@kulla.think.com.UUCP (Barry
  Margolin) writes:
    Note that Lispms aren't the only Lisps with CDR-coding.  I believe
    that a number of Lisps for conventional processors do CDR-coding these
    days.  It's a time/space tradeoff in these cases.
  Whoa!  Which ones do you know for sure do cdr-coding??  I've not seen
  any myself, even after an extensive survey of systems, which wasn't
  surprising because you lose big if you don't have hardware support for
  forwarding ptrs...

Eclisp, a Lisp for the Data General Eclipse computers, used internally
at Data General, used cdr-coding.  It may have exploited a "go inderect"
that could be placed in a location (if indeed the Eclipse had such
bits).  "Conventional processors" can cover quite a variety of
machines.

Jeff Dalton,                      JANET: J.Dalton@uk.ac.ed             
AI Applications Institute,        ARPA:  J.Dalton%uk.ac.ed@nss.cs.ucl.ac.uk
Edinburgh University.             UUCP:  ...!ukc!ed.ac.uk!J.Dalton