Re: `unreadablep'

[Po Lu]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> There's perhaps a slight performance issue -- if the unreadable object
> is the first in a long list, we could have exited a lot sooner, but I'm
> not sure that's really much of an issue in practice.  If it is, we could
> perhaps change PRINTCHARFUN to take two arguments in this case, where
> the second is EVERYTHING-IS-READABLE-SO-FAR, and then PRINTCHARFUN could
> throw an error if it wishes...
>
> Or, as has been suggested, add a new print-* variable to have the same
> effect -- it'd fit in with the current design (of having a bunch of
> print-* variables).

Yes, now I think the `print-unreadable-function' solution would be best;
we could just cause a non-local exit from within that function.