all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Thierry Volpiatto' <thierry.volpiatto@gmail.com>,
	'Stefan Monnier' <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: RE: persistent lisp objects
Date: Thu, 08 Oct 2009 14:11:55 +0900	[thread overview]
Message-ID: <87zl82qxk4.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E9DB2351D7C5404D9F320583D1CECBA0@us.oracle.com>

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.





  reply	other threads:[~2009-10-08  5:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  8:50 persistent lisp objects Thierry Volpiatto
2009-10-01  8:14 ` Thierry Volpiatto
2009-10-07 16:53   ` Drew Adams
2009-10-07 22:03     ` Stefan Monnier
2009-10-07 22:10       ` Drew Adams
2009-10-08  5:11         ` Stephen J. Turnbull [this message]
2009-10-25 10:33           ` Thierry Volpiatto
2009-10-25 10:26       ` Thierry Volpiatto
2009-10-25 15:05         ` Stefan Monnier
2009-10-27 20:18         ` Ted Zlatanov
  -- strict thread matches above, loose matches on Subject: below --
2009-10-02 20:55 MON KEY
2009-10-03  3:36 ` Stefan Monnier
2009-10-03 19:19   ` MON KEY
2009-10-03 20:13 ` Richard Stallman
2009-10-04  0:15   ` MON KEY
2009-10-04 21:03     ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zl82qxk4.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=thierry.volpiatto@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.