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: Instead of pcase Date: Thu, 04 Jan 2024 23:23:47 -0500 Message-ID: References: <878r5inysw.fsf@localhost> <878r5ewk81.fsf@localhost> <87h6jxm8d4.fsf@localhost> <87a5pm762w.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="21158"; 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 Fri Jan 05 05:24:52 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 1rLblL-0005G9-J3 for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Jan 2024 05:24:51 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rLbkL-0002H7-4X; Thu, 04 Jan 2024 23:23:49 -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 1rLbkK-0002Gp-5V for emacs-devel@gnu.org; Thu, 04 Jan 2024 23:23:48 -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 1rLbkJ-0005kM-He; Thu, 04 Jan 2024 23:23:47 -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=ARvllqFYWA5Clfi49r97k1T/HkHtjSup0NthgRTH36w=; b=CdEgI50gry94 /q27A1gsGz+ga8RTMLfDLwNSoIbdG1oATED8bbfJFe55VstMuQAyLB0Koc1Tfl0si/jB4YO9nBhpV 3IFrKPA/N7XOTN/T5CyaDp7IO23Ake0upy8cIPV8ZS79u5doCrTfizF4ld/kCanghI5pcYOwNxP7H sypyLukTcnbrqdZOgdQNLcWt4n2fhJEuDWoO1Vnd26Bp2YazozJgNn683gIUWqLn6Yb6Bqn/neBEt EO5br+SDUyZnTc66kiz6B8KC3kD6aisWU8QJu28cHYTP9kdaQi8+7eVyabIzUqChZVfUtZQvo08RH R6VtnC/V711Mx0tSeW/fTw==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1rLbkJ-0000EJ-9X; Thu, 04 Jan 2024 23:23:47 -0500 In-Reply-To: <87a5pm762w.fsf@localhost> (message from Ihor Radchenko on Wed, 03 Jan 2024 16:08:23 +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:314554 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. ]]] > Consider another example: > (match* (xor (not var) t) t) My first repsonse was to say that xor is not valid in cond* patterns. Indeed, I did not know that this function `xor' existed. But now I see that your example does fit the definition of cond* patters, and its meaning is quite unintuitive. I wonder why people defined `xor'. It can't be used as a conditional, like `and' and `or', so what is the point of it? Anyway, I suppose the best response is to say that such counterintuitive constrained variables are best avoided. Or else specifically disallow `xor' as PRED in a constrained variable. -- 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)