From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Shrinking the C core Date: Mon, 11 Sep 2023 15:05:56 +0300 Message-ID: <83sf7krk2j.fsf@gnu.org> References: <87ledwx7sh.fsf@yahoo.com> <877cpfybhf.fsf@yahoo.com> <873503y66i.fsf@yahoo.com> <87v8cmft42.fsf@yahoo.com> <8734zqo6eo.fsf@dataswamp.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33101"; mail-complaints-to="usenet@ciao.gmane.io" Cc: incal@dataswamp.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 11 14:07:29 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 1qffhQ-0008Nl-Ov for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Sep 2023 14:07:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qffgP-0002ZK-6C; Mon, 11 Sep 2023 08:06:25 -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 1qffgN-0002Z6-0b for emacs-devel@gnu.org; Mon, 11 Sep 2023 08:06:23 -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 1qffgK-0006jJ-IN; Mon, 11 Sep 2023 08:06:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=0GocCDWxA3BIQ3u1Sdk7kpw4a4sI0KUdd30BjPb9SDU=; b=jwHwP32arId9 Cp0W0TY2yeNDyG5uHERjwOq9N+RG7aY/4ezCgpt1faWtZJqqD7H61fUmU1IvwFoUBhpWY31G56uIP qhQT9adV6pb8nUutu7U8bHU3zWzMX8ypF1oMfPm8FXWzOnfQ8vPWeLJ/cldqDnTsjScadnPv3DzC7 dpeSaiXCTp2VObmchgr0z7yAIZTRLqEoJPY0D95WYcwOwiiL0trtP6C+zyTIN+blK02VMRMpFMtAE clBEKwroktVXEqrc7hpiqB2ruLIlP3EcHXArQnmyXV4reow1F8tjWcXeK5qR/68z+KJt78vNzkGg3 TbduvSKKj02bh+4DLVst6A==; In-Reply-To: (message from Richard Stallman on Sun, 10 Sep 2023 20:43:01 -0400) 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:310462 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Sun, 10 Sep 2023 20:43:01 -0400 > > The cl libraries of Emacs Lisp define functions that are not standard > parts of Emacs Lisp. They are not documented in the Emacs Lisp > Reference Manual -- for good reason (we don't want to write that > documentation or have a commitment to maintain ever after later). As > a consequence, code which uses those constructs is extra work to > understand and to maintain. This particular aspect -- documentation -- is somewhat blurred these days: you will find some "cl-*" functions in the ELisp manual. (Typing "i cl- TAB" in the ELisp manual produces 5 completion candidates.) So we do document some cl functions when we find that useful. > If you want to use them in your own private code, that's no problem > for anyone else -- do what you feel like, there. Using them in a > not-terribly-vital package that you maintain and some others use is > not a big drawback. However, using them in code others need to > maintain makes maintaining Emacs harder. > > I do not say "impossible", but it is worth avoiding. This message is in many cases met with opposition and thus is not easy to send in practice.