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: cond* Date: Sun, 07 Jan 2024 22:47:12 -0500 Message-ID: References: <87frzuae9n.fsf@posteo.net> <871qbatqc8.fsf@posteo.net> <87wmsz7lzn.fsf@posteo.net> <87edf1m7lq.fsf@localhost> <87cyui76l9.fsf@localhost> <871qauy1io.fsf@localhost> 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="2998"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 08 04:47:46 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 1rMgc6-0000ZB-3M for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Jan 2024 04:47:46 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rMgbg-0001c0-9f; Sun, 07 Jan 2024 22:47:20 -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 1rMgbe-0001bM-F9 for emacs-devel@gnu.org; Sun, 07 Jan 2024 22:47:18 -0500 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 1rMgbe-00044H-2f; Sun, 07 Jan 2024 22:47:18 -0500 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=sh2hdT2v8pnx8PtH2Dv28BOW5CsUa1c9zg8zuW8yrfo=; b=Nho2cooG21UI FvVo+zV5qtwuXW3JwWj4DqQZLOyHKH4+HwrDRvk2m1jgsC3SLE6K6VFmeeYqRx1iBVOxyOHMidlCm p4aMF5jR6u/Un8cqUjV+tKpGZhF1tn5h9yt4zO+kcs951ynGcjKQM54G9J3D9TyBO1SAKJyleJ9eC 44GGVLSdx9TspDvutxpZxOEW3vbbZ5yzGlmuwgiGuM3RyTOEQ7zhDYXIkRLPyZczjoWlqaRnr7UhU j/8jxApmp/CoJ+BAaXrbR4gBdw31PEhzyBI1cBkwLpRaOdDrCApnFo/s6x7uxPwtZOnxcNmSxzo2E +492XFt4YnC/OdnlhV7mAA==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1rMgbY-0002ib-It; Sun, 07 Jan 2024 22:47:12 -0500 In-Reply-To: <871qauy1io.fsf@localhost> (message from Ihor Radchenko on Sat, 06 Jan 2024 14:33:51 +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:314727 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. ]]] > In particular, I believe that (PRED ...) in conf* is no > less confusing than (pred ...) that pcase provides. A few people misunderstood it from the initial version of the documentation, but that is no reason to think the feature itself is confusing. The corresponding pcase `pred' feature is certainly not better -- it is inside out -- and I don't see any other alternative to try. If you would like to suggest one, I'd look at it with interest. IMHO, the recursive > (PRED1 (PRED2 ...) ...) is more confusing compared to what pcase offers. You may be right about that. I decided to remove it, for now. I introduced a `and' construction which is like the one in pcase. It can be used for the same purposes and may be more natural. Thanks for working with me. -- 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)