From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Registry warning?
Date: Thu, 29 Sep 2011 19:52:08 +0200 [thread overview]
Message-ID: <87zkhngrsn.fsf@randomsample.de> (raw)
In-Reply-To: <87k48rn423.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 29 Sep 2011 03:30:44 -0500")
Ted Zlatanov writes:
> On Thu, 29 Sep 2011 08:02:01 +0200 David Engster <deng@randomsample.de> wrote:
>
> DE> Ted Zlatanov writes:
>>> On Wed, 28 Sep 2011 09:29:33 +0200 David Engster <deng@randomsample.de> wrote:
>
> DE> No. If you look in your mails somewhere around May, you'll see I wrote
> DE> this to you when discussing ERT tests on Emacs 22. EIEIO cannot
> DE> magically save any LISP structure (what about recursive structures, for
> DE> example?). It uses prin1 and hopes for the best, but you can provide
> DE> your own printer in the ':printer' slot.
>>>
>>> Thanks for repeating the information, I either forgot or misunderstood
>>> it. So can we provide a custom printer for Emacs 23.1 and older?
>
> DE> Yes, for some definition of "we" (read: not me). ;-)
>
> Is there an API for this printer? What functions must it provide? We
> can just reuse the old registry save/load code.
It must do what `prin1' does, minus the optional PRINTCHARFUN
argument. That means, it has to print the slot in a way that can later
be understood by `read'. See also section 3.2 of the EIEIO info:
(info "(eieio)Slot options")
-David
prev parent reply other threads:[~2011-09-29 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 20:24 Dave Goldberg
2011-09-04 21:01 ` David Engster
2011-09-04 21:07 ` Dave Goldberg
2011-09-27 21:49 ` Ted Zlatanov
2011-09-28 7:29 ` David Engster
2011-09-29 0:21 ` Ted Zlatanov
2011-09-29 6:02 ` David Engster
2011-09-29 8:30 ` Ted Zlatanov
2011-09-29 17:52 ` David Engster [this message]
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=87zkhngrsn.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).