Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: =~ doesn't work with NUL characters

X-seq: zsh-workers 41304
From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: Re: =~ doesn't work with NUL characters
Date: Thu, 15 Jun 2017 08:38:46 +0100
Cms-type: 201P
In-reply-to: <20170614204938.GA76510@tower.spodhuis.org>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Organization: Samsung Cambridge Solution Centre
References: <20170613100217.GA9529@chaz.gmail.com> <CGME20170614210706epcas2p1b78fb2088d5605b9077798f2102c0e17@epcas2p1.samsung.com> <20170614204938.GA76510@tower.spodhuis.org>

On Wed, 14 Jun 2017 16:49:38 -0400
Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx> wrote:
> Thus: do we want to change behaviour, after 16 years, to allow embedded
> NUL for the PCRE case, being different from the ERE case?

I don't see why not --- the behaviour with NUL may be longstanding but
it's a bit cloudy what the actual intention is.  Generally, accepting
NUL as a regular character anywhere we can get it to work and shrugging
our shoulders in cases where the system fails to support it seems
reasonable to me.

pws

References:
- =~ doesn't work with NUL characters
  - From: Stephane Chazelas
- Re: =~ doesn't work with NUL characters
  - From: Phil Pennock

Messages sorted by: Reverse Date, Date, Thread, Author