From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: RE: persistent lisp objects Date: Thu, 08 Oct 2009 14:11:55 +0900 Message-ID: <87zl82qxk4.fsf@uwakimon.sk.tsukuba.ac.jp> References: <871vlqt9rv.fsf@tux.homenetwork> <87ljjv5y5b.fsf@tux.homenetwork> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1254978237 3992 80.91.229.12 (8 Oct 2009 05:03:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 8 Oct 2009 05:03:57 +0000 (UTC) Cc: 'Thierry Volpiatto' , 'Stefan Monnier' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 08 07:03:46 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MvlAB-000055-NW for ged-emacs-devel@m.gmane.org; Thu, 08 Oct 2009 07:03:39 +0200 Original-Received: from localhost ([127.0.0.1]:37303 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MvlAB-0001Jn-8I for ged-emacs-devel@m.gmane.org; Thu, 08 Oct 2009 01:03:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MvlA2-0001JA-Lc for emacs-devel@gnu.org; Thu, 08 Oct 2009 01:03:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mvl9y-0001IZ-4F for emacs-devel@gnu.org; Thu, 08 Oct 2009 01:03:30 -0400 Original-Received: from [199.232.76.173] (port=34305 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mvl9x-0001IW-NY for emacs-devel@gnu.org; Thu, 08 Oct 2009 01:03:25 -0400 Original-Received: from mtps02.sk.tsukuba.ac.jp ([130.158.97.224]:44578) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mvl9x-0001aH-14 for emacs-devel@gnu.org; Thu, 08 Oct 2009 01:03:25 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps02.sk.tsukuba.ac.jp (Postfix) with ESMTP id 86482820F; Thu, 8 Oct 2009 14:03:18 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id E4AB31A267E; Thu, 8 Oct 2009 14:11:55 +0900 (JST) In-Reply-To: X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta29) "garbanzo" baeb249ab9b1+ XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:115977 Archived-At: 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.