From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: persistent lisp objects Date: Sun, 25 Oct 2009 11:05:05 -0400 Message-ID: References: <871vlqt9rv.fsf@tux.homenetwork> <87ljjv5y5b.fsf@tux.homenetwork> <87hbtn6a6t.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 1256483127 4008 80.91.229.12 (25 Oct 2009 15:05:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 Oct 2009 15:05:27 +0000 (UTC) Cc: emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 25 16:05:20 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 1N24em-0003rk-7A for ged-emacs-devel@m.gmane.org; Sun, 25 Oct 2009 16:05:20 +0100 Original-Received: from localhost ([127.0.0.1]:36133 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N24el-0006ax-F2 for ged-emacs-devel@m.gmane.org; Sun, 25 Oct 2009 11:05:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N24ef-0006aj-2l for emacs-devel@gnu.org; Sun, 25 Oct 2009 11:05:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N24eZ-0006Zo-Kr for emacs-devel@gnu.org; Sun, 25 Oct 2009 11:05:11 -0400 Original-Received: from [199.232.76.173] (port=38203 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N24eZ-0006Zl-FN for emacs-devel@gnu.org; Sun, 25 Oct 2009 11:05:07 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:53632 helo=ironport2-out.pppoe.ca) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N24eY-0008QG-VJ for emacs-devel@gnu.org; Sun, 25 Oct 2009 11:05:07 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtkEAEcF5EpLd/xb/2dsb2JhbACBT9JhhD8EiDQ X-IronPort-AV: E=Sophos;i="4.44,621,1249272000"; d="scan'208";a="48130739" Original-Received: from 75-119-252-91.dsl.teksavvy.com (HELO pastel.home) ([75.119.252.91]) by ironport2-out.pppoe.ca with ESMTP; 25 Oct 2009 11:05:05 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id AB6A98225; Sun, 25 Oct 2009 11:05:05 -0400 (EDT) In-Reply-To: <87hbtn6a6t.fsf@tux.homenetwork> (Thierry Volpiatto's message of "Sun, 25 Oct 2009 11:26:50 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:116394 Archived-At: >> I have no idea what he thinks as novel, but such functions have been >> available for ages. Called print and read. [...] > That is surely not the best way to serialize objects, but that is better > than nothing until somebody write something to save hash-table, lists, > etc... in a data base. Again, what's wrong with print&read? That's what your eval-when-compile uses. All the eval-when-compile does is to let the byte-compiler serialize an object into a .elc file. If you're not limited to a .elc file, then it seems a lot simpler to just use print&read directly. Stefan