From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Phil Sainty Newsgroups: gmane.emacs.devel Subject: Re: Naming FCRs Date: Wed, 29 Dec 2021 14:02:00 +1300 Message-ID: References: <01d516b3-86ca-fdf3-73f0-49b2e6930499@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40487"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Orcon Webmail Cc: Stefan Monnier , Emacs developers To: Jim Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 29 02:03:10 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n2NN0-000AN6-8j for ged-emacs-devel@m.gmane-mx.org; Wed, 29 Dec 2021 02:03:10 +0100 Original-Received: from localhost ([::1]:51414 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n2NMz-0002uW-5y for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Dec 2021 20:03:09 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40226) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2NM2-0002Ec-2A for emacs-devel@gnu.org; Tue, 28 Dec 2021 20:02:10 -0500 Original-Received: from smtp-3.orcon.net.nz ([60.234.4.44]:33219) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2NM0-0000b7-62 for emacs-devel@gnu.org; Tue, 28 Dec 2021 20:02:09 -0500 Original-Received: from [10.253.37.70] (port=1844 helo=webmail.orcon.net.nz) by smtp-3.orcon.net.nz with esmtpa (Exim 4.90_1) (envelope-from ) id 1n2NLs-0001xM-JP; Wed, 29 Dec 2021 14:02:00 +1300 Original-Received: from ip-139-180-110-102.kinect.net.nz ([139.180.110.102]) via [10.253.37.253] by webmail.orcon.net.nz with HTTP (HTTP/1.1 POST); Wed, 29 Dec 2021 14:02:00 +1300 In-Reply-To: X-Sender: psainty@orcon.net.nz X-GeoIP: -- Received-SPF: pass client-ip=60.234.4.44; envelope-from=psainty@orcon.net.nz; helo=smtp-3.orcon.net.nz X-Spam_score_int: 0 X-Spam_score: 0.0 X-Spam_bar: / X-Spam_report: (0.0 / 5.0 requ) FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:283527 Archived-At: On 2021-12-29 07:35, Jim Porter wrote: > For me at least, the benefit of "function object" is that it's > already the established name for something like this in the C++ > world[1]. When I think of a function object, I think (in C++) > of a class/struct that holds some data but exists primarily to > be used as a function (typically by passing it to a > metafunction). > > However, for non-C++ programmers, I can see how it would give > the wrong connotation. Yes, in a lisp context I think it would just be confusing? Functions are already (lisp) objects. The specific object type may vary from function to function, but if someone said "function object" to me I wouldn't think they meant anything more than one of the existing types of object that a function can be.