From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Re: New rx implementation with extension constructs Date: Thu, 5 Sep 2019 18:49:23 +0200 Message-ID: <0D601D4F-B6CF-44D1-A8C1-28A51EE850A2@acm.org> References: <1C71289F-C5D5-4F9C-947C-374110C1D572@acm.org> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="25676"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 05 18:49:38 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1i5uwz-0006YY-BS for ged-emacs-devel@m.gmane.org; Thu, 05 Sep 2019 18:49:37 +0200 Original-Received: from localhost ([::1]:48350 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i5uwx-00064Q-VQ for ged-emacs-devel@m.gmane.org; Thu, 05 Sep 2019 12:49:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42644) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i5uwr-000646-Nr for emacs-devel@gnu.org; Thu, 05 Sep 2019 12:49:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i5uwq-0007Kq-BE for emacs-devel@gnu.org; Thu, 05 Sep 2019 12:49:29 -0400 Original-Received: from mail214c50.megamailservers.eu ([91.136.10.224]:57352 helo=mail193c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i5uwp-0007Jf-PL for emacs-devel@gnu.org; Thu, 05 Sep 2019 12:49:28 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1567702165; bh=J7m84AA/CcSdfOta/u8VMqcggnHxZlI5ZbGfOmdY674=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=iMfEsY4K/2wJhBwF8fzxnajVf9SdAaS0BCEEcIRSDr/fHgETKKWlOQe1ldfYibFwv aMrIV7UEKDGrvaSEOd84qValc5ApVNIZr8GyroMiGf/y01vmcJQ1kEvCDfK02ybT35 8LGZ6wA0Ssv1E8/nRkI7n4Ks3jf0tzBJPjCX7ytI= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.0.4] ([188.150.171.71]) (authenticated bits=0) by mail193c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id x85GnN4D017201; Thu, 5 Sep 2019 16:49:25 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3445.104.11) X-CTCH-RefID: str=0001.0A0B0201.5D713C95.0025, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.3 cv=ZLb5Z0zb c=1 sm=1 tr=0 a=SF+I6pRkHZhrawxbOkkvaA==:117 a=SF+I6pRkHZhrawxbOkkvaA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=M51BFTxLslgA:10 a=pGLkceISAAAA:8 a=Aa7SuUCzwkx6wYdb618A:9 a=CjuIK1q_8ugA:10 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 91.136.10.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:239873 Archived-At: 5 sep. 2019 kl. 17.38 skrev Noam Postavsky : >=20 > Do you mean that macros don't support (literal LISP-FORM) and (regexp > LISP-FORM)? Or something else? No, those work just as before. I just meant that user-defined rx forms = work by plain substitution and have no computational power. They are = more like C macros than Lisp macros in that respect. But you are quite right --- `literal', `regexp' or `eval' could be = (ab)used to get computing macros, so it isn't really a limitation. > It would help to add some concrete examples (i.e., of things that > would count as `t', `seq', etc) to this abstract explanation. Thanks, will do. >> +(defun rx--translate-symbol (sym) >> + "Translate an rx symbol. Return (REGEXP . PRECEDENCE)." >> + (pcase sym >> + ((or 'nonl 'not-newline 'any) (cons (list ".") t)) >=20 > Is there a reason not to use '((".") . t) here (and similar for the = rest > of the alternatives)? If yes, then it's probably worth mentioning in = a > comment. It's because they may be fed into mapcan; I'll add a comment (or maybe = use something non-destructive). Thank you. > If not using string-to-multibyte, I think this lambda can be replaced > with #'unibyte-char-to-multibyte. Didn't know about that one, thank you!