From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Distinguishing `consp` and `functionp` Date: Wed, 31 Jan 2024 13:34:35 -0500 Message-ID: References: <86msssble8.fsf@gnu.org> <86bk9448ai.fsf@gnu.org> <864jew40m3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37822"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 31 19:36:48 2024 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 1rVFS3-0009ec-Pi for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Jan 2024 19:36:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rVFRI-0006IJ-90; Wed, 31 Jan 2024 13:36:00 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rVFRG-0006Hs-1w for emacs-devel@gnu.org; Wed, 31 Jan 2024 13:35:58 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rVFRE-0004UI-6e for emacs-devel@gnu.org; Wed, 31 Jan 2024 13:35:57 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 88F5F441ABC; Wed, 31 Jan 2024 13:35:53 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1706726152; bh=PLmxpwZskUiUBDiy8LiFJURcxR6z2vdlAdjUPr1BAUc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=czPmSLenLujAzbjdgcfRbADWNweaUBEIK9NxR0A0jeStX22DIbebkjR9yVhmqIRvw O7tXz2J5Me4M52WL3Ld1ZPFb6znrUnNREvhwTyWAxuikEQCZCq/Qj8bdMs9We7N4Y9 Sgk1bxbXhl6qy7t2HXCmwTaePzRjqvqf1Bj3aQYmGVSTDGzmkI5vQ8uzFveb5/cVQ0 aRCTZl42omJFzcRXeUNl6fwl36K83h2pvKkBZAFQh5+etKiwkbK1qXlfwpBr9Kchql lnFxe1cPtTo5aI5wsU0g1syaS7d4ncZTaIvLnm1CoC0MyagewaDRng+nEx28PpY9Mq ep/uhb26sN6iw== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 56851441A87; Wed, 31 Jan 2024 13:35:52 -0500 (EST) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4605B120AA9; Wed, 31 Jan 2024 13:35:52 -0500 (EST) In-Reply-To: (=?windows-1252?Q?=22Jo=E3o_T=E1vora=22's?= message of "Wed, 31 Jan 2024 10:51:07 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:315679 Archived-At: > ...apart from working with legacy code, of course. So as I said I > really think you should leave functionp returning t for a good > while and warn about the funcall. In any case, currently we can't know if a `(lambda ...)` list is the result of "broken code" or is a perfectly valid function value returned by `Ffunction` from a dynbound file. So before we can contemplate such a warning, we need to either drop dynbound interpreted code, or use a patch along the lines of what I sent :-) Stefan "whose local Emacs hacks don't support dynbound code any more and signal an error when `funcall` is passed a list :-)"