From: LdBeth <andpuke@foxmail.com>
To: monnier@iro.umontreal.ca
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Naming FCRs
Date: Mon, 27 Dec 2021 13:46:20 +0800 [thread overview]
Message-ID: <tencent_B8ABE43F0AB795EE5F47C29E2B0C6C9D1107@qq.com> (raw)
In-Reply-To: <E1n1hPz-0001cv-9t@fencepost.gnu.org>
> The current name stands for FunCallableRecords, but this name is clearly
> wrong, since it makes it sound like I'm defining a special kind of
> record that just happen to be callable as a function, whereas FCRs are
> really fundamentally functions that happen to have slots and a type,
> like records.
I'm not sure, is this feature similar to "Flavors" or "Entifies"
avaliable from Lisp Machine?
To quote from Lisp Machine Manual
> An entity is almost the same thing as a closure; an entity behaves
> just like a closure when applied, but it has a recognizably
> different data type which allows certain parts of the system such as
> the printer and describe to treat it differently. A dosurc is simply
> a kind of ·function, but an entity is assumed to be a
> message-receiving object. Thus, when the Lisp printer (sec section
> 23.1, page 506) is given a closure, it prints a simple textual
> representation, but when it is handed an entity~ it sends the entity
> a :print-self message, which the entity is expected to handle. The
> describe function (sec page 791) also sends entities messages when
> it is handed them. So when you want to make a message-receiving
> object out of a closure, as described on page 407, you should usc an
> entity instead.
--
LDB
next prev parent reply other threads:[~2021-12-27 5:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 22:04 Naming FCRs Stefan Monnier
2021-12-26 22:29 ` Dmitry Gutov
2021-12-27 18:55 ` Stefan Monnier
2021-12-28 0:31 ` Dmitry Gutov
2021-12-27 0:46 ` Bob Rogers
2021-12-28 13:11 ` xenodasein--- via Emacs development discussions.
2021-12-29 16:33 ` Lars Ingebrigtsen
2022-01-04 20:31 ` Stefan Monnier
2022-01-11 3:25 ` Filipp Gunbin
2022-01-11 3:44 ` Stefan Monnier
2022-01-12 4:56 ` Richard Stallman
2022-01-12 15:10 ` Stefan Monnier
2021-12-27 1:35 ` Po Lu
2021-12-27 2:33 ` Qiantan Hong
2021-12-27 4:12 ` Stefan Monnier
2021-12-27 7:33 ` tomas
2021-12-29 1:09 ` Phil Sainty
2021-12-28 4:19 ` Richard Stallman
2021-12-28 5:43 ` Po Lu
2021-12-28 11:24 ` Andreas Schwab
2021-12-28 17:28 ` Stefan Monnier
2021-12-30 10:35 ` Andreas Schwab
2021-12-27 4:15 ` Richard Stallman
2021-12-27 5:46 ` LdBeth [this message]
2021-12-27 19:48 ` Stefan Monnier
2021-12-27 4:38 ` Jim Porter
[not found] ` <jwvczlheu3o.fsf-monnier+emacs@gnu.org>
2021-12-28 18:35 ` Jim Porter
2021-12-29 1:02 ` Phil Sainty
2021-12-29 16:19 ` Richard Stallman
2021-12-29 16:43 ` [External] : " Drew Adams
2021-12-29 19:01 ` Stefan Monnier
2021-12-30 2:54 ` LdBeth
2021-12-30 4:28 ` Richard Stallman
2021-12-30 8:43 ` tomas
2021-12-30 10:15 ` Tomas Hlavaty
2021-12-30 14:00 ` Stefan Monnier
2021-12-30 18:46 ` Tomas Hlavaty
2021-12-31 4:26 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_B8ABE43F0AB795EE5F47C29E2B0C6C9D1107@qq.com \
--to=andpuke@foxmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).