From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Naming FCRs
Date: Tue, 28 Dec 2021 02:31:36 +0200 [thread overview]
Message-ID: <5f16f3f7-831b-1458-ed13-c40a83b3ea01@yandex.ru> (raw)
In-Reply-To: <jwvpmphev87.fsf-monnier+emacs@gnu.org>
On 27.12.2021 21:55, Stefan Monnier wrote:
> Dmitry Gutov [2021-12-27 00:29:29] wrote:
>> On 27.12.2021 01:04, Stefan Monnier wrote:
>>> - Monomaniac objects (since they're a bit like OO-style objects but
>>> limited to have only exactly one method).
>> A function with a value attached sounds like a "method".
>
> Hmm... in my mind a method is more like a function attached to a (set
> of) objects.
In Ruby object model anyway, a Method is a method bound to a particular
instance of a class (https://ruby-doc.org/core-2.7.1/Method.html),
whereas for methods not bound to any given value the term is "unbound
method" (https://ruby-doc.org/core-2.7.1/UnboundMethod.html).
Though I suppose one semantic distinction is that when one thinks about
methods, some "class" is present in the context, and one would usually
expect that said class should contain other methods as well (i.e. the
value that is said method is bound to, can respond to some other
methods), which matters to how one organizes code. But... that's not
necessarily true when one considers CLOS or our cl-defmethod, right?
Anyway, perhaps an unambiguous term could be "bound method".
Or if we take JavaScript, the return value of Function#bind
(https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind)
is described as "bound function". But JS uses the word "function" for
both "normal" functions and methods, so I suppose "bound method" would
be less ambiguous.
On the third hand, the adjective hints at some action of "binding" which
is supposed to produce such values, which is true of both Ruby and JS
examples. If there is nothing similar going on in fcr.el, maybe such
term wouldn't be ideal.
>> Not too fun, though.
>
> There's a fair bit of potential by playing with the "meth" prefix, I think.
Following the glorious tradition of "gimp", "git" and "slime".
>> I also looked at the branch briefly -- if it's what it sounded like then you
>> might be setting up a new "Callable protocol" which can allow any object to
>> serve as a function, not just records? Like how maps are callable
>> in Clojure.
>
> Not really. It's more about adding object characteristics to functions than
> adding function characteristics to objects.
All right, then.
next prev parent reply other threads:[~2021-12-28 0:31 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 [this message]
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
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=5f16f3f7-831b-1458-ed13-c40a83b3ea01@yandex.ru \
--to=dgutov@yandex.ru \
--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 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).