> How does this relate to the requirement that (define car 42) shall not
> affect the behavior of any built-in procedure?
It is because of the forward-and-backward effect of redefinition that the
standard felt the need to include that requirement! They fit together like
hand and glove.
The solution is that built-in procedures be lexically protected against
user redefinitions. This can be accomplished either by having an
interaction-environment that's different from the one where the primitives
live, or by doing
(define append
(let ((car car) (cdr cdr) ...)
(lambda ...)))
> Can you explain what this "jewel" language is?
Oh, you know, R4RS. Minus the macro appendix. (Yes, I get it that you
were being sarcastic.)
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
