Re: -pcre-match doesn't work since version 5.4.1

[Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>]

[ SWITCHED TO -workers ]

On 2017-08-10 at 21:07 -0400, Phil Pennock wrote:
> On 2017-08-11 at 00:29 +0200, nimaje+zml@xxxxxxxxxxxxxx wrote:
> > after upgrading to version 5.4.1 I noticed that using -pcre-match doesn't
> > work
> > 
> > % zmodload zsh/pcre; [[ 'dxd' -pcre-match ^d+$ ]]
> > 
> > zsh: unknown condition: -pcre-match
> 
> I see this too; none of the loadable infix operators seem to be working,
> so it's not specific to the PCRE module.  -regex-match doesn't work
> either.

No fix yet, still investigating the commit which broke.

With a git bisect script (below) and:
  git bisect start HEAD zsh-5.3.1 --
  git bisect run ../bisect-script
git spits out that:

------------------------8< git bisect result >8-------------------------
f3f8537cfa05414ad14494e809d9ebfeef86ebbc is the first bad commit
commit f3f8537cfa05414ad14494e809d9ebfeef86ebbc
Author: Peter Stephenson <pws@xxxxxxx>
Date:   Tue Mar 7 10:43:58 2017 +0000

    40760: Always tokenize unquoted - to Dash.

    This fixes use of pattern match character ranges in unusual contexts.

    Attempt to detect a tokenized - in cases where we don't care.
------------------------8< git bisect result >8-------------------------

-------------------------8< ../bisect-script >8-------------------------
#!/bin/sh -eu
make
ln -nsf . Src/Modules/zsh
./Src/zsh -fc '
module_path=( /Users/pdp/src/zsh/code/Src/Modules )
zmodload zsh/pcre
[[ foo -pcre-match ^f..$ ]]
'
-------------------------8< ../bisect-script >8-------------------------