Re: hash-table-{to, from}-alist

[Stefan Monnier]

> The #s kind of bothers me.  In common lisp, #s(a ...) is readable - as an
> instance of struct a [*]. Hence the "s". Now, hashtables may well use
> a struct for their metadata as an implementation detail, but the #s<...>
> does look to me like an odd mix of commmon lisp #s(...)
> struct-instance-literal syntax and #<...>
> printable-but-unreadable-object syntax.

For what it's worth:

   % clisp
     i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
     I I I I I I I      8     8   8           8     8     o  8    8
     I  \ `+' /  I      8         8           8     8        8    8
      \  `-+-'  /       8         8           8      ooooo   8oooo
       `-__|__-'        8         8           8           8  8
           |            8     o   8           8     o     8  8
     ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8
   
   Welcome to GNU CLISP 2.44.1 (2008-02-23) <http://clisp.cons.org/>
   
   Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
   Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
   Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
   Copyright (c) Bruno Haible, Sam Steingold 1999-2000
   Copyright (c) Sam Steingold, Bruno Haible 2001-2008
   
   Type :h and hit Enter for context help.
   
   [1]> (let ((x (make-hash-table))) (setf (gethash 4 x) 6) x)
   #S(HASH-TABLE :TEST FASTHASH-EQL (4 . 6))
   [2]> 

So the question is should we use #s(...) as CL does, or #s<...> as
XEmacs does.


        Stefan