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: Tue, 26 Dec 2023 23:54:24 -0500 Message-ID: References: <87frzuae9n.fsf@posteo.net> <871qbatqc8.fsf@posteo.net> 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="4226"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 27 05:55:16 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 1rILwq-0000ny-C3 for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Dec 2023 05:55:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rILw7-0007Ke-C7; Tue, 26 Dec 2023 23:54:31 -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 1rILw2-0007KN-7Z for emacs-devel@gnu.org; Tue, 26 Dec 2023 23:54:26 -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 1rILw0-00047g-9G; Tue, 26 Dec 2023 23:54:25 -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=QAEcCjM7WItc0IW+4+f0H1KM+ifRT6WkHLJXHD1u2iU=; b=NhA3aJXtHH9+ tKq7ronteJjhkNowvkIikRywtoZpGXSjLlq5dozWxOmpJ14+eY65hmH18e25tmtvBhjmMdxIVx+wG 3gpF+OyRlhVbRr3rPe2ZZuuiiYNhFmEVYHq3f4X0OYvC1sY0UJtfaGy7SnX+pl7TxhuzYstQMPDvQ wKHwVmO/+/6WYs0UqpRZR9JfFQ6stUaFfisrj2TOMYPBeCN8pMbRfgGankwcb3ZurYQ5HdvlxdUjV ysdmZvx7OMq1IwG632NjT3OW5CZj1QgV3gqWoVwLwSXgx2IhrrKRgFoSuthI7tkbxa2S7DP8bv3v8 T/IO3BVTDMm/AawQWjsDYQ==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1rILw0-0006UT-1a; Tue, 26 Dec 2023 23:54:24 -0500 In-Reply-To: <871qbatqc8.fsf@posteo.net> (message from Philip Kaludercic on Mon, 25 Dec 2023 12:32:39 +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:314235 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. ]]] > Having a rough prototype of an implementation would still be useful to > have, to get a better felling of what the macro should look and feel > like. Yes, it might do that. Would you like to help write it? I think some parts of the pcase code could be adapted. > E.g. from reading your messages, I am > still not sure how `cond*' and `match' are supposed to interact with one > another. `match*' is not an independent construct defined on its own. It is meaningful only within a cond* construct. In effect, it marks a certain part of the cond*. If someone can figure out a way that `match*' could be meaningful on its own, whi;e also working together with `cond*' so that the two function together as desired, that would be a neat hack. But I'm not aiming for that. -- 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)