Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbage
From: jonl%kuwait@LUCID.COM (Jon L White)
Newsgroups: comp.lang.clos
Subject: Problem - compiling PCL on Mips running Lucid 4.0beta
Message-ID: <9104151956.AA11008@kuwait>
Date: 15 Apr 91 19:56:08 GMT
References: <9104151704.AA02742@cs.rpi.edu>
Sender: welch@tut.cis.ohio-state.edu
Distribution: inet
Organization: CommonLoops
Lines: 22

re: Should every occurrence of LCL3.0 in PCL be changed to
    (or LCL3.0 LCL4.0) in May Day PCL?

No.  I'm cc'ing the broader list now just in case anyone else is uncertain
about the meaning of Lucid's *FEATURES* entries.

:LCL3.0  is not a release-specific marker, but implies the existence
of a set of capabilites and featuers that were introduced first during
the 3.0 release timeframe.  Similarly, the appearance of :LCL4.0 does
NOT imply the retraction of any :LCL3.0 features.


However, one item is worth looking in to.  The  #+LCL3.0  version of
(defmacro without-interrupts (&body body) ...)  was an attempt to
work around a performance gap in the 3.0 release.  But subsequent
releases have reduced the overhead cost of WITH-INTERRUPTS-DEFERRED
to that of a single UNWIND-PROTECT; so the workaround kludge needn't
be relevant anymore (and I don't even think it was used in PCL, but
just in case . . . )


-- JonL --