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: icalendar.el bug fix patch Date: Fri, 1 Nov 2019 22:38:49 +0100 Message-ID: <66FE4C1F-B166-42A6-A8EA-C37973072DF7@acm.org> References: <875zkfd1rz.fsf@hm.sivalik.com> <83eeyslytn.fsf@gnu.org> <87imo3g8af.fsf@hm.sivalik.com> <831rurn3vs.fsf@gnu.org> <321C5595-5EBF-4231-9179-FE1CA4A412F7@acm.org> <83tv7nlo16.fsf@gnu.org> <34fad408-c220-7980-c7fe-1299093d842f@cs.ucla.edu> 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="199957"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Eli Zaretskii , rajeev@sivalik.com, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 01 22:42:12 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 1iQegO-000prF-1O for ged-emacs-devel@m.gmane.org; Fri, 01 Nov 2019 22:42:12 +0100 Original-Received: from localhost ([::1]:43162 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iQegL-0003oq-HF for ged-emacs-devel@m.gmane.org; Fri, 01 Nov 2019 17:42:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36244) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iQedS-0003oe-2V for emacs-devel@gnu.org; Fri, 01 Nov 2019 17:39:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iQedO-000545-GC for emacs-devel@gnu.org; Fri, 01 Nov 2019 17:39:08 -0400 Original-Received: from mail150c50.megamailservers.eu ([91.136.10.160]:55784 helo=mail50c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iQedM-0004Uw-Sf; Fri, 01 Nov 2019 17:39:05 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1572644332; bh=2covuSjSrG/MXlAgJ7T0f5erPvKBYlF66PWOLZTWQ0w=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=byRufllb2x1L+KUGj3LlrexhuCnLWfusOWHglE1vRfON+CGmRS6++u0mU50owoiuk o54kcxgtY2N/46MetjD613Bjzg1+b5mN66V127bkEKt8QHmngfzzLmX1eFxCVlbwf/ KAL29ADf148Ck9Th+i/Tc6Fx37RvMzSLAss+fmGM= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.1.64] (c-ac4be655.032-75-73746f71.bbcust.telenor.se [85.230.75.172]) (authenticated bits=0) by mail50c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id xA1LcnWs018170; Fri, 1 Nov 2019 21:38:51 +0000 In-Reply-To: <34fad408-c220-7980-c7fe-1299093d842f@cs.ucla.edu> X-Mailer: Apple Mail (2.3445.104.11) X-CTCH-RefID: str=0001.0A0B020D.5DBCA5EC.000F, 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=N4FX6F1B c=1 sm=1 tr=0 a=7cLsWLGj2bcc4bLyp6BeEw==:117 a=7cLsWLGj2bcc4bLyp6BeEw==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=M51BFTxLslgA:10 a=fI8zdlnRzqV3HVs65FwA:9 a=CjuIK1q_8ugA:10 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy] X-Received-From: 91.136.10.160 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:241713 Archived-At: 1 nov. 2019 kl. 22.19 skrev Paul Eggert : > But since the concept is useful, how about if we create an escape for = it? For example, we could establish \! as a regexp that matches any = single character. This be more readable than either [^z-a] or \(?:.\| > \), and would surely help performance as well as readability. Some time ago I experimented with adding a regexp-engine opcode for = anychar, but didn't observe any significant difference in performance = from that of [^z-a] or \Sq. It is possible that gains could be had if = the opcode were to be exploited on a deeper level, such as producing a = fast scan loop for [^z-a]*STRING. One has to be careful with = backtracking, however. This is orthogonal to the addition of regexp string syntax for anychar = (like \!); neither requires the other.