RE: persistent lisp objects

[Stephen J. Turnbull]

Drew Adams writes:

 > print and read are no good for objects whose print form is not
 > readable by the reader. That's the general problem (lack) in this
 > regard.

Some objects (frames, for example) *cannot* have a readable print form
because they refer to objects that Emacs in principle cannot print
(GUI windows, in the case of frames).  For objects that can but don't,
the right thing to do is to file a bug against `print' and `read', not
request that an obscure hack be sanctified.

Cf. the recent creation of a read'able print representation for hash
tables.