all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: persistent lisp objects
Date: Sun, 25 Oct 2009 11:05:05 -0400	[thread overview]
Message-ID: <jwvpr8bh5yd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87hbtn6a6t.fsf@tux.homenetwork> (Thierry Volpiatto's message of "Sun, 25 Oct 2009 11:26:50 +0100")

>> 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




  reply	other threads:[~2009-10-25 15:05 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
2009-10-25 10:33           ` Thierry Volpiatto
2009-10-25 10:26       ` Thierry Volpiatto
2009-10-25 15:05         ` Stefan Monnier [this message]
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=jwvpr8bh5yd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --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.