[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SETF and sequence updater's return values
- To: GSB at MIT-ML
- Subject: SETF and sequence updater's return values
- From: Carl W. Hoffman <CWH at MIT-MC>
- Date: Mon, 24 Aug 81 21:52:00 GMT
- Cc: JONL at MIT-MC, BUG-LISP at MIT-MC, NIL at MIT-MC
- Original-date: 24 August 1981 17:52-EDT
Date: 24 August 1981 02:17-EDT
From: Glenn S. Burke <GSB at MIT-ML>
... my personal feeling is that the returned value should
be undefined. My own versions of setf, even the one written for
protosystem 3 years ago, have always had the macro SETV which was
like SETF but did guarantee the returned value.
In addition to allowing SETF optimizations, I feel this approach makes
code easier to read by tagging places in which an assignment is also used
for value.