Re: Un-deprecating oset

[Philippe Vaucher]

> Deprecating (oref object slot value)
> in favor of (setf (oref object slot) value)
> does *nothing* to increase "namespace sanity", the declared goal.
> It does however take away the programmers choice whether to use
> `setf' or not, but only when it comes to OOP, which seems unfair.

If I followed correctly the first line should read "(oset object slot
value)" (not oref), but I think most people will be able to
autocorrect.