[Bese-devel] (setf container.current-component) returns t when the set actually happened

Attila Lendvai attila.lendvai at gmail.com
Wed Jun 7 13:24:32 UTC 2006


> setf methods must return the new value, i don't think this is actually
> written anywhere in the standard but every single setf method i have
> ever seen does this.
>
> why was this change made?

in my code i'm using this to do different things if the setf actually happened.

i was considering this issue myself, but i've never seen code relying
on the return value of setf.

doing the check for the current component from outside the container
code needs to rely on container behaviour/internals, so it's not an
option.

so, i'm open to suggestions! maybe there should be a
set-current-component that does the same as the setf but returns this
extra information?

-- 
- attila

(alias 101 on irc &no 'its not lisp code :)



More information about the bese-devel mailing list