Re: bind commands that change buffer contents to `undefined' when read-only?

[Richard Stallman]

    So maybe a better direction is to change the toplevel so that using
    a command with a "*" (or a call to barf-if-buffer-read-only) in its
    interactive spec when the buffer is read-only will signal "undefined" rather
    than signalling the error.

That is clean and simple, but I think it is a change for the worse.
Sorry, but no thanks.