Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Kupfer <mike.kupfer@xemacs.org>
To: ding@gnus.org
Subject: XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el)
Date: Sat, 01 Jun 2013 15:04:13 -0700	[thread overview]
Message-ID: <6219.1370124253@rawbw.com> (raw)
In-Reply-To: My message of "Mon, 27 May 2013 17:43:56 PDT." <201305280043.r4S0hvFT030018@shell0.rawbw.com>

Mike Kupfer wrote:

> David Engster wrote:
> > Another example is the registry, which is not persistent under XEmacs
> > because it lacks a printed representation for hash tables.
> 
> Interesting; thanks.  It looks like 21.5 has a printed representation,
> but the output from #'print can't be fed back to #'read.  I'll file an
> XEmacs bug.

I looked into this some more.  It turns out that #'print et al can be
told to use a read-able representation for hash tables; it's just not
the default.  To get a read-able representation, you first have to bind
print-readably to t, as in

  (setq myhash (make-hash-table))
  (let ((print-readably t)) (prin1-to-string myhash))

I suggested making the read-able representation the default, but that
was rejected.

Does Gnus need to preserve the hash table metadata (rehash-size et al)?
I was wondering if it would work just as well for Gnus to use an alist
as the external representation for a hash table.

regards,
mike




  reply	other threads:[~2013-06-01 22:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 19:23 XEmacs builds failing - gnus-spec.el Adam Sjøgren
2013-05-19 21:45 ` Mike Kupfer
2013-05-19 21:58   ` Adam Sjøgren
2013-05-19 22:13     ` Adam Sjøgren
2013-05-19 23:30       ` Adam Sjøgren
2013-05-20  7:39         ` David Engster
2013-05-20 16:01           ` Adam Sjøgren
2013-05-20 16:36             ` Adam Sjøgren
2013-05-20 23:55               ` Katsumi Yamaoka
2013-05-21 21:01                 ` Adam Sjøgren
2013-05-21 23:39                   ` Katsumi Yamaoka
2013-05-22  2:58                     ` Mike Kupfer
2013-05-22  5:45                       ` Katsumi Yamaoka
2013-05-28  0:22                         ` Mike Kupfer
2013-05-31 12:07                           ` Mats Lidell
2013-05-22 20:18                     ` Adam Sjøgren
2013-05-22 20:28                       ` Adam Sjøgren
2013-05-22 20:36                     ` David Engster
2013-05-28  0:43                       ` Mike Kupfer
2013-06-01 22:04                         ` Mike Kupfer [this message]
2013-06-02  8:59                           ` XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el) David Engster
2013-06-02 16:22                             ` Mike Kupfer
2013-06-06 14:46                               ` Ted Zlatanov
2013-06-06 16:06                                 ` Mike Kupfer
2013-05-22  3:02           ` XEmacs builds failing - gnus-spec.el Mike Kupfer
2013-05-22 20:25             ` David Engster
2013-05-28  0:25               ` Mike Kupfer

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=6219.1370124253@rawbw.com \
    --to=mike.kupfer@xemacs.org \
    --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).