From: Tianxiang Xiong <tianxiang.xiong@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Print representation of records and hash tables
Date: Wed, 13 Dec 2017 19:33:35 -0800 [thread overview]
Message-ID: <CACMkxizEJiTHB0wLx846A=hov_icPKxXgR4hBBKk=tYA5OCK_A@mail.gmail.com> (raw)
In-Reply-To: <jwvpo7jsnm7.fsf-monnier+gmane.emacs.devel@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
@Stefan, perhaps it'd be helpful to explain *why* `#s` was chosen. I'd
guess it's to fit with the `#s` read macro for structures
<https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node191.html> in CL?
It's too bad hash tables already use `#s`--`#{`
<http://frank.kank.net/essays/hash.html> or `#h` <http://cl21.org/> would
be more appropriate.
On Tue, Dec 12, 2017 at 12:22 PM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >>> Yes, it's confusing, and I'm very much against it. Interpretation of
> ELisp
> >>> code (even compiled code) now changes in a very subtle manner
> depending on
> >>> whether a record named `hash-table` happens to be defined or not.
> SM> Similarly, interpretation of Elisp code can change in a very subtle
> SM> manner if someone does (fset 'apply (lambda ...)).
> > OK, but the read behavior is more broken. Right now records have
> > basicall taken over all #s
>
> No, only those that are not taken by other uses.
>
>
> Stefan
>
>
>
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
next prev parent reply other threads:[~2017-12-14 3:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 10:32 Print representation of records and hash tables Tianxiang Xiong
2017-12-11 21:20 ` Philipp Stephani
2017-12-12 15:21 ` Stefan Monnier
2017-12-12 17:12 ` Ted Zlatanov
2017-12-12 20:22 ` Stefan Monnier
2017-12-14 3:33 ` Tianxiang Xiong [this message]
2017-12-14 14:19 ` Stefan Monnier
2017-12-14 5:22 ` Ted Zlatanov
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='CACMkxizEJiTHB0wLx846A=hov_icPKxXgR4hBBKk=tYA5OCK_A@mail.gmail.com' \
--to=tianxiang.xiong@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.