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: Default lexical-binding to t Date: Fri, 08 Nov 2024 13:43:20 -0500 Message-ID: References: <86ttcnuppm.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="3109"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Jim Porter , Eli Zaretskii , rms@gnu.org, emacs-devel@gnu.org To: John Yates Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 08 19:43:54 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 1t9TxZ-0000h9-Qs for ged-emacs-devel@m.gmane-mx.org; Fri, 08 Nov 2024 19:43:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t9TxI-0001eE-Ut; Fri, 08 Nov 2024 13:43:36 -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 1t9Tx8-0001bo-ES for emacs-devel@gnu.org; Fri, 08 Nov 2024 13:43:26 -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 1t9Tx7-0007EP-2B; Fri, 08 Nov 2024 13:43:26 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 5A6E444462E; Fri, 8 Nov 2024 13:43:22 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1731091401; bh=MreduEBBVGUorpdzMpcUZNoYHedF29Gx3a11NPePGn8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=e8kjHVkEe+ytvFi8s7bfsF7lcSvet6eMxH8btQZZEKDUxRH96xyzHcgHYFrd+QJdH NszjZoGY1vYplEX1qGjDvrQ7r4wWN8nbYIovXYdv31A5qB316LlYBchTq3VHf2SUkz PL9JzCthgQJTV9dGaLI3MwLqmRVNg5OULqmZ3kHfSKEQ1siiWh3iKT5PHIsUGYelGV 9ntSXMSDfvhZY2wLHq0bOmsBqgPbC9EhLIqaqripgxdx1kNchm1K0DZv9ziCz0Ajxz PSOcnyH1N1iLqd9WxvQuLzZO+zhv0GLu3+aRpa1lyv2z+0T8w0KMJ2jGPeJccOh2Sw dWauFKpN2d7aQ== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 53D7F44462D; Fri, 8 Nov 2024 13:43:21 -0500 (EST) Original-Received: from asado (bras-base-mtrlpq0776w-grc-08-184-145-223-228.dsl.bell.ca [184.145.223.228]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 42B0B12033B; Fri, 8 Nov 2024 13:43:21 -0500 (EST) In-Reply-To: (John Yates's message of "Wed, 6 Nov 2024 15:23:24 -0500") 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325305 Archived-At: > Being fundamentally a programmer in languages that support only lexical > binding, I have little sense of the mechanics underlying dynamic binding. > That said, I wonder if something along these line could help a bit: > > If a "void variable" error is about to be thrown and the source defaulted > to dynamic binding then > > - Perform a dynamic lookup of the offending variable > > > - If the lookup is unsuccessful then issue the same error as always > > > - If the lookup is successful, then modify the diagnostic to mention > the possibility of a dynamic / lexical binding clash That's already what happens. Stefan