zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: please consider using PCRE_DOLLAR_ENDONLY (and PCRE_DOTALL) for rematchpcre
Date: Mon, 22 Jan 2018 00:28:29 -0500	[thread overview]
Message-ID: <20180122052829.GA83799@tower.spodhuis.org> (raw)
In-Reply-To: <180119234824.ZM7254@torch.brasslantern.com>

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


  reply	other threads:[~2018-01-22  5:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 12:25 Stephane Chazelas
2017-11-22 21:40 ` Stephane Chazelas
2018-01-20  7:48   ` Bart Schaefer
2018-01-22  5:28     ` Phil Pennock [this message]
2018-01-23  6:57       ` Stephane Chazelas
2018-01-23 13:55         ` Stephane Chazelas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180122052829.GA83799@tower.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).