From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Lisp files that load cl-lib in problematical ways Date: Sat, 21 Oct 2023 01:21:16 -0400 Message-ID: References: <83fs3dgxv8.fsf@gnu.org> <835y38qvlg.fsf@gnu.org> <87bkcx6eci.fsf@dataswamp.org> <83ttqnm4ti.fsf@gnu.org> <83lebyu5yx.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4370"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 21 07:21:35 2023 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 1qu4QZ-0000w3-5C for ged-emacs-devel@m.gmane-mx.org; Sat, 21 Oct 2023 07:21:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qu4QJ-0005Vk-1V; Sat, 21 Oct 2023 01:21:19 -0400 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 1qu4QG-0005V9-Mg for emacs-devel@gnu.org; Sat, 21 Oct 2023 01:21:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qu4QG-00067X-EI; Sat, 21 Oct 2023 01:21:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=wCMCGkeYDD2j1Ab5q0n8joqH2lvo7rSSWN/kCpOrEMI=; b=QAz7/5Lu0IeZ 5DYIVoRX+opSBtIe5N+5TksLVghZNhBjaD9TRLRDs28QYC8toB6lqeouMBcD+yxISg3Zwv4KWH0oA d/sgmdD9CZdSsZ8VyOevFlXRfY6KGwA7qP1Er+xEz/VfJZC0G8xrN7XiMzpEIegVjJfsRvGPmusmO +QuHHkYMLrR85XVMTEUo1SDT4Jr/LpGymbPX5KCA5wgPvRPBtMX+2qBbYBKz8lxOsbwzVuTg+Cg0Y JcXO3ZK7AXymdFxYSmGqMU7HK4Kiy36ncyT82uQ1+qs02g4zdzSW4q1OWWJko6BYmMcmjTAbJUYEP 6bHrB+kbI8BQgRhkUuHk2g==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1qu4QG-0005HG-0t; Sat, 21 Oct 2023 01:21:16 -0400 In-Reply-To: (message from Alan Mackenzie on Thu, 19 Oct 2023 13:28:28 +0000) 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:311635 Archived-At: [[[ 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. ]]] > Quite a lot of the function calls are things like cl-assert, cl-incf, or > cl-defgeneric, which won't cause the loading of cl- until they are > actually run. Those are macros, right? These macros are not supposed to need cl-lib at run time; they are supposed to be handled (when the code is compiled) at compile time. Maybe people changed these macros and caused them to load cl-lib. But maybe not all of them. I looked into cl-assert and found that it generates a call to cl--assertion-failed, which is defined in xo cl-preloaded.el. So I think that macro is ok -- the problem in question doesn't seem to happen in cl-assert. Which of the cl- macros really generate calls that require cl-lib to be loaded? We should fix those. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)