Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!killer!pollux!ti-csl!mips!gateley
From: gateley@mips.csc.ti.com (John Gateley)
Newsgroups: comp.lang.lisp
Subject: Re: Protection of core lisp fns (was: Re: Question about eval)
Message-ID: <61560@ti-csl.CSNET>
Date: 21 Oct 88 18:57:47 GMT
References: <13733@iuvax.cs.indiana.edu> <20700006@iuvax> <29266@think.UUCP> <589@dcl-csvax.comp.lancs.ac.uk>
Sender: news@ti-csl.CSNET
Reply-To: gateley@mips.UUCP (John Gateley)
Organization: TI Computer Science Center, Dallas
Lines: 14

In article <589@dcl-csvax.comp.lancs.ac.uk> simon@comp.lancs.ac.uk (Simon Brooke) writes:
>[...]
>abandon. And if we aren't allowed to redefine the way the top-level read - eval
>- print loop works, then the language certainly isn't as expressive: there is
>a large category of things it can't express.
>** Simon Brooke *********************************************************

Sure you can express these things if you want to: there is always *eval-hook*
and if that is not powerful enough, then you can write your own
read-eval-print loop. What you cannot do is redefine a symbol in the lisp
package. You can, however, by use of CL's package system, define your own
eval which would take the place of CL's eval in your programs only.

John
gateley@mips.csc.ti.com