From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Shrinking the C core Date: Wed, 13 Sep 2023 08:34:36 +0200 Message-ID: <87r0n2eg3n.fsf@dataswamp.org> References: <87ledwx7sh.fsf@yahoo.com> <877cpfybhf.fsf@yahoo.com> <873503y66i.fsf@yahoo.com> <87v8cmft42.fsf@yahoo.com> <8734zqo6eo.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40933"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:KsLqYWZdt3mbaRTwgpAsqGtnxmk= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 13 13:07:41 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 1qgNif-000AQE-Cl for ged-emacs-devel@m.gmane-mx.org; Wed, 13 Sep 2023 13:07:41 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qgNiN-0007BO-0L; Wed, 13 Sep 2023 07:07:24 -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 1qgJSd-0004cq-Pd for emacs-devel@gnu.org; Wed, 13 Sep 2023 02:34:51 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qgJSa-0001ZC-9p for emacs-devel@gnu.org; Wed, 13 Sep 2023 02:34:51 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qgJSX-0007lh-AE for emacs-devel@gnu.org; Wed, 13 Sep 2023 08:34:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Wed, 13 Sep 2023 07:07:17 -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:310540 Archived-At: Richard Stallman wrote: > The cl libraries of Emacs Lisp define functions that are not > standard parts of Emacs Lisp. What is the definition of standard Emacs Lisp, stuff that don't have to be `require'd? Because cl-lib is part of vanilla Emacs, you don't have to install it, even from GNU ELPA or any such other official source. It is there. > 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). cl-lib should of course be documented like everything else, and it is. But just as an experiment, I run (checkdoc-current-buffer t) in the cl-lib.el buffer and it had 14 remarks. One could do that for the other cl-lib files as well. cl-lib.el:133: Argument ‘keys’ should appear (as KEYS) in the doc string cl-lib.el:160: All variables and subroutines might as well have a documentation string cl-lib.el:166: All variables and subroutines might as well have a documentation string cl-lib.el:197: All variables and subroutines might as well have a documentation string cl-lib.el:197: All variables and subroutines might as well have a documentation string cl-lib.el:226: Arguments occur in the doc string out of order cl-lib.el:258: Argument ‘specs’ should appear (as SPECS) in the doc string cl-lib.el:357: Argument ‘cl-func’ should appear (as CL-FUNC) in the doc string cl-lib.el:450: Argument ‘rest’ should appear (as REST) in the doc string cl-lib.el:488: Argument ‘cl-item’ should appear (as CL-ITEM) in the doc string cl-lib.el:501: Argument ‘cl-new’ should appear (as CL-NEW) in the doc string cl-lib.el:510: All variables and subroutines might as well have a documentation string cl-lib.el:539: All variables and subroutines might as well have a documentation string cl-lib.el:577: Probably "returns" should be imperative "return" GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, cairo version 1.16.0) of 2023-09-08 [commit a2f977d94e0356c7414876e988adedd2ab7b52f2] > code which uses those constructs is extra work to understand > and to maintain. But then what are we gonna use instead of `cl-decf', `cl-incf', `cl-labels', `cl-map' and so on? -- underground experts united https://dataswamp.org/~incal