From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: Naming FCRs Date: Thu, 30 Dec 2021 09:43:40 +0100 Message-ID: References: <01d516b3-86ca-fdf3-73f0-49b2e6930499@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xr+CVMWuuj65u49d" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1512"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 30 09:44:25 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 1n2r2u-0000C6-VU for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Dec 2021 09:44:25 +0100 Original-Received: from localhost ([::1]:35214 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n2r2t-000219-F9 for ged-emacs-devel@m.gmane-mx.org; Thu, 30 Dec 2021 03:44:23 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:36856) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2r2H-0001MO-RU for emacs-devel@gnu.org; Thu, 30 Dec 2021 03:43:45 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]:35954) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n2r2F-0002Zd-PG for emacs-devel@gnu.org; Thu, 30 Dec 2021 03:43:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=+QReMMPXO9g0HbH2iQLgtvp1I5MZtRlkmh2284PBQVY=; b=Cz/XMEwg/FVqU06Tx/vBzk4i9Q 0kyGfTPadC4ZGBgjnuEM48XPzFcpL/ROZ5vn7aKy1hMEG/trsdLlo4zHxEUGmJt1UEgeab7Xos+eE lDcWvBQXJJLsa1+X5lIV373zsloD3Tp9kS4Io9pZ6tSK5ExhYuTntpI3a9ADtDammIvelbvLrzoYm uZ3eixE3YmQYUEBW1FzCd2ls/4huJJ795bJ7joxifBHrToajOxwF4Zh+hspXNX/AYFaJ7uTXC3nq7 76SuhRRt+6ix2S86OLVY6+coEi2lqpXPH2fJitiDEIZnauYktGX6OgwNm6UW2A9pF3+hMXnDb3s51 h+uzHf2A==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.94.2) (envelope-from ) id 1n2r2C-0001tg-S0 for emacs-devel@gnu.org; Thu, 30 Dec 2021 09:43:40 +0100 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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:283626 Archived-At: --xr+CVMWuuj65u49d Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 29, 2021 at 11:28:41PM -0500, Richard Stallman wrote: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] >=20 > > > I think we should extend the functionality of closures by providing= a > > > way to access the bound variables in them. Then we won't need to m= ake > > > Emacs Lisp more complicated with a new data type, because ordinary > > > closures will do this job too. >=20 > > That's exactly what fcr.el does. >=20 > I have not seen fcr.el -- would you please send me a copy? >=20 > However, if it does exactly what I described above, why do we need a > name other than "closures"? Why do we need a new type of object? Possibly because it diverges somewhat from the canonical meaning of "closure" -- it might confuse people. Cheers --=20 t --xr+CVMWuuj65u49d Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCYc1xNgAKCRAFyCz1etHa RsmlAJ9QrGDN9uOqqVTD9bKijgSzMVpmRACfZJzP4+mQTJsSuGEh/v8JK8CxVRA= =ntul -----END PGP SIGNATURE----- --xr+CVMWuuj65u49d--