Newsgroups: comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!nntp.sei.cmu.edu!fs7.ece.cmu.edu!hudson.lm.com!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!agate!library.ucla.edu!csulb.edu!csus.edu!netcom.com!NewsWatcher!user
From: vanmeule@acm.org (Andre van Meulebrouck)
Subject: Re: why is set! not called set ?
Message-ID: <vanmeule-0204951701520001@192.0.2.1>
Sender: vanmeule@netcom20.netcom.com
Organization: nil
References: <3lf1p4$6rs@apollo.jcpenney.com> <BLUME.95Mar30171825@atomic.cs.princeton.edu>
Date: Mon, 3 Apr 1995 00:01:51 GMT
Lines: 16

In article <BLUME.95Mar30171825@atomic.cs.princeton.edu>,
blume@atomic.cs.princeton.edu (Matthias Blume) wrote:

> Your expectation is wrong.  SET! mutates the *location* X is bound to.

[responding to this message since the original is no longer on the server]

In addition to the fact that the bang (!) indicates mutation, there is
another issue worth mentioning (even if it's somewhat orthogonal).  

SET historically was a function that evaluated all its arguments, whereas
set! doesn't evaluate it's first (odd) argument(s).

;;;;;;;;;;;;;;;;;;;;  Andre van Meulebrouck  ;;;;;;;;;;;;;;;;;;;;;
;;  e-mail:  vanmeule@acm.org     finger:  vanmeule@netcom.com  ;;
;;;;;  URL:  ftp://ftp.netcom.com/pub/va/vanmeule/home.html  ;;;;;
