[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SETF
- To: JONL at MIT-MC (Jon L White)
- Subject: Re: SETF
- From: Dave Touretzky at CMU-10A
- Date: Thu, 14 Aug 80 03:55:00 GMT
- Cc: bug-lisp at MIT-MC
- In-reply-to: JONL@MIT-MC's message of 13 Aug 80 22:41-EST
- Original-date: 13 August 1980 2355-EDT
Clearly the return value of SETF should be X. Returning whatever random
piece of structure was returned by the operation SETF expanded to is
not very esthetic. What happens if, for some SETF cases, SETF is
changed or improved in some way? Then the result of some SETF
expansions might change, and this wouldn't be very pleasant. If SETF
always returned its second argument its behavior would be guaranteed
consistent, and also simpler.