Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!ucbvax!cs.umass.edu!DAVID%COUSTEAU
From: DAVID%COUSTEAU@cs.umass.edu (David Forster)
Newsgroups: comp.sys.ti.explorer
Subject: CL compatibility.
Message-ID: <2830219305-6378196@Cousteau>
Date: 8 Sep 89 04:01:45 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 17

I don't see the setting of sys::*inhibit-displacing-flag* as a `bug' so much as
a (possibly) faulty policy decision.  I think the default ought to be whatever
makes the machine run fastest, but it should definitely be settable in the
profile.  Forgive the analogy, but it's like DEC's FORTRAN compiler having a switch to
check for adherence to ANSI standards -- their default is to use their own dialect, but
you can force strict checks by setting the appropriate command line switch.

I agree with the suggestion to have some easy way to force strict CL semantics.
It might be specified as an extra parameter to ticl::turn-common-lisp-on.

By the way, sys::*inhibit-displacing-flag* is documented, though deeply buried
(section 18.5) in the lisp reference manual.  I don't know if there's a section
of the documentation labelled something like ``Strict Common LISP
Compatibility,'' but there ought to be.  It would be the ideal place for such
items as this.

- David