From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Bob Rogers Newsgroups: gmane.emacs.devel Subject: RE: [External] : Re: What's missing in ELisp that makes people want to use cl-lib? Date: Tue, 7 Nov 2023 10:16:13 -0800 Message-ID: <25930.32493.606314.802027@orion.rgrjr.com> References: <46ab3c7d-d820-4bb4-8ec4-97c614d7c8a0@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28190"; mail-complaints-to="usenet@ciao.gmane.io" Cc: To: Drew Adams , Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 07 19:17:30 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 1r0Qdm-00078c-CJ for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Nov 2023 19:17:30 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r0Qcl-0006I2-Np; Tue, 07 Nov 2023 13:16:27 -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 1r0Qci-0006Hg-NS for emacs-devel@gnu.org; Tue, 07 Nov 2023 13:16:24 -0500 Original-Received: from mail-oa1-x30.google.com ([2001:4860:4864:20::30]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1r0Qcb-0004DU-MA for emacs-devel@gnu.org; Tue, 07 Nov 2023 13:16:24 -0500 Original-Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-1ead2e6fab7so3561641fac.0 for ; Tue, 07 Nov 2023 10:16:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rgrjr-com.20230601.gappssmtp.com; s=20230601; t=1699380975; x=1699985775; darn=gnu.org; h=references:in-reply-to:subject:cc:to:date:message-id :content-transfer-encoding:mime-version:from:from:to:cc:subject:date :message-id:reply-to; bh=cKtQKM44/6HLPO/ArOu/CXOb1Za3cvyWOr62QjQzQ2Q=; b=WHlrrPekVOg3yBjIk2tTCaN5vgaPMjOIAQaIFUDG4SAdW0/5+nyGmVet5xYrSncTpP R49FNHtQRv8BS9/K/un/XhqmtrexbhYZlpwW8CN6Jhzc84mhPDDFSNNAp8PJP1nnQGJy BsVEhGHABS3as/EwZhawc15iekHiWALnRNWjDtuyRQLxJY4jEgLICpc93Xo/Bb01qUCA lrfQCh8Y1HDdkgMR4QhkwfgE9+B/njJzHEjMXNM+sqPiSl2KKbnlALpa4tqQ+NiK8ck2 C2DXSkmmDH2gKJ0epLioktFF0v1Y7runDR9K5ojX9tpFiWiHHOlLtwOn+rwP0zBZbey1 WFDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699380975; x=1699985775; h=references:in-reply-to:subject:cc:to:date:message-id :content-transfer-encoding:mime-version:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=cKtQKM44/6HLPO/ArOu/CXOb1Za3cvyWOr62QjQzQ2Q=; b=JR0Q9K/GS89t1HzwmGa40kyr1wBdKZo5zssy9PFQSb/j37ogIvtLWurTko+RsWsWmB Sh2lGdNkupGYvktpVud00GgeW4GorMV6/NERlWg/K606aWYmKxKzbeo6XGk2wgWvLQ7W Nm4Zawv5kstAg8o8rSDPVML2Bt1PjmcmRy1Hep4CEBx9yFCvo5I58Mm3z8X/zSt+zNE0 2c0MuvcG5A1T1u+94H5RHlw5LxyF/w5t76HVvWLIhV8Ak/FNHWmY28CPXPErakRTvhtV xgvN0rvb5gGgFJjS4vP1pNob4tlCW2o4mKX4UxepgzwG4emzQUL4+3WFp7d+SacJmhXD 0ulQ== X-Gm-Message-State: AOJu0Yz1fgYpwdZDt61TZ+J7IsUMBAeABrd9VTrqpYC4ZLlPMVxjvLD+ 3ocd7243yypVrMxaa1W32hPhdQ== X-Google-Smtp-Source: AGHT+IGNn9VHLnnO9ieA+iFwei4VbiDXJmu00C9hJDRSKjKa6+Ob6XWrTgJzawVu10XN7t/15QsaZA== X-Received: by 2002:a05:6870:d90:b0:1ef:3916:2d80 with SMTP id mj16-20020a0568700d9000b001ef39162d80mr3903669oab.46.1699380975096; Tue, 07 Nov 2023 10:16:15 -0800 (PST) Original-Received: from orion.rgrjr.com ([2600:1700:7c2c:e000::22]) by smtp.gmail.com with ESMTPSA id k24-20020a635618000000b005b9083b81f0sm1699334pgb.36.2023.11.07.10.16.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Nov 2023 10:16:14 -0800 (PST) X-Google-Original-From: Bob Rogers In-Reply-To: X-Mailer: VM 8.2.0b under 30.0.50 (x86_64-pc-linux-gnu) Received-SPF: none client-ip=2001:4860:4864:20::30; envelope-from=rogers@rgrjr.com; helo=mail-oa1-x30.google.com 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, NICE_REPLY_A=-2.344, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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:312318 Archived-At: From: Drew Adams Date: Tue, 7 Nov 2023 16:39:16 +0000 > > There's a difference between (1) adding &key to > > Elisp generally and (2) letting more functions > > take advantage of :key and :test, in particular. > > That is a valid distinction. > > I would be happy to see a keyword argument facility provided for > function definitions in Emacs Lisp. There are occasions where it is > good for a function to accept keyword arguments -- especially those > functions that need to accept lots of arguments . . . FWIW, to me, all of what you say there is welcome news . . . Likewise. I have especially wished for a native &key; I think it will greatly help Elisp code readability. -- Bob