From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1747 invoked by alias); 22 Jan 2018 05:46:26 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 42316 Received: (qmail 4632 invoked by uid 1010); 22 Jan 2018 05:46:26 -0000 X-Qmail-Scanner-Diagnostics: from mx.spodhuis.org by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(94.142.241.89):SA:0(-4.2/5.0):. Processed in 1.855429 secs); 22 Jan 2018 05:46:26 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: zsh-workers+phil.pennock@spodhuis.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201711; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding :Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=UR0J2z5xkYPlLaBo3BmHwWA9i9vf+N+La1RhsXCuxVU=; b=hLPhkLOX4bVlTuZD3N0k+YaPVH 65Hhkk3RKmCpIjU6V2Y4XkOdWUUAgQkbkP6N1i35+GrCjd1J3z3lr/qtd3JLXYi+2aJ4AdKz8U1z5 qIbV5CbjDtiL4qljNjsQVjKIN3MUvEqw5q/j0N9HFbwYS6eMDEFB4LCf8Z3AEYtWqE/KegPU5zkub qhBTSs72hQXM+V68umSwzxLpCIST; Date: Mon, 22 Jan 2018 00:28:29 -0500 From: Phil Pennock To: Bart Schaefer Cc: zsh-workers@zsh.org Subject: Re: please consider using PCRE_DOLLAR_ENDONLY (and PCRE_DOTALL) for rematchpcre Message-ID: <20180122052829.GA83799@tower.spodhuis.org> References: <20171122122519.GA13771@chaz.gmail.com> <20171122214025.GA2992@chaz.gmail.com> <180119234824.ZM7254@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <180119234824.ZM7254@torch.brasslantern.com> OpenPGP: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc On 2018-01-19 at 23:48 -0800, Bart Schaefer wrote: > Another one that seems to have lost traction. Holiday malaise? > (workers/42044) Speaking only for myself: the =~ for PCRE is a thin wrapper around the long-standing PCRE module (introduced in 2001) and that in turn is a thin wrapper around the PCRE defaults. Changing the default behavior of valid semantics risks hard-to-debug breakage of existing scripts and I am erring on the side of being against this change. It's not hard opposition, but I'd like to see stronger justification before risking breaking changes. I know that I myself have scripts which rely upon PCRE matching against multiline data behaving as per the defaults of pcrepattern(3). In addition, while the DOTALL change can be turned off in-regex, the dollar-endonly one can't, AFAIK, so that becomes a breaking change which can't be worked around. -Phil