Re: Buffer names are sometimes read-only objects in daemonized emacs

[Wojciech Meyer]

Tassilo Horn <address@hidden>  writes:

> IMO a function shouldn't need to allow modification of it's return value
> explicitly, but instead should warn if that's possible.  But indeed,
> evaluating
>
>   (aset (buffer-name) 0 ?g)

How would you do this? I see that the check can be performed on only at
runtime. Bytecompiler will not warn, because the value might be
propagated, and Lisp is dynamicaly typed. (in simple cases like this it
is apparent, but consider just returning this value from function).

Wojciech