From @khwilliamson

Patterns like /_?[^\W_0-9/ against a UTF-8 target string stopped working as of commit bcb8752 in 5.19.8.

Something like the _? is crucial in this bug, as it causes the regex optimizer to generate a synthetic start class (SSC), though there are lots of other ways to force one, and the bug only happens with the SSC.

Karl Williamson

From @Tux

On Sat, 13 Feb 2016 14​:33​:09 -0800, Karl Williamson (via RT)
<perlbug-followup@​perl.org> wrote​:

Patterns like /_?[^\W_0-9/ against a UTF-8 target string stopped
working as of commit bcb8752 in
5.19.8.

missing a ]

did you mean /_?[^\W_0-9]/ ?

Something like the _? is crucial in this bug, as it causes the regex
optimizer to generate a synthetic start class (SSC), though there are
lots of other ways to force one, and the bug only happens with the
SSC.

--
H.Merijn Brand http​://tux.nl Perl Monger http​://amsterdam.pm.org/
using perl5.00307 .. 5.23 porting perl5 on HP-UX, AIX, and openSUSE
http​://mirrors.develooper.com/hpux/ http​://www.test-smoke.org/
http​://qa.perl.org http​://www.goldmark.org/jeff/stupid-disclaimers/

The RT System itself - Status changed from 'new' to 'open'

From @khwilliamson

On 02/14/2016 01​:12 AM, H.Merijn Brand wrote​:

On Sat, 13 Feb 2016 14​:33​:09 -0800, Karl Williamson (via RT)
<perlbug-followup@​perl.org> wrote​:

Patterns like /_?[^\W_0-9/ against a UTF-8 target string stopped
working as of commit bcb8752 in
5.19.8.

missing a ]

did you mean /_?[^\W_0-9]/ ?

Yes

Something like the _? is crucial in this bug, as it causes the regex
optimizer to generate a synthetic start class (SSC), though there are
lots of other ways to force one, and the bug only happens with the
SSC.

From @khwilliamson

This was fixed in ac33c51
--
Karl Williamson

@khwilliamson - Status changed from 'open' to 'pending release'

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.\n\nWith the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved. Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0

@khwilliamson - Status changed from 'pending release' to 'resolved'

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.\nWith the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved. Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.

With the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved. Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.

With the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved.
Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.

With the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved.

Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0

From @khwilliamson

Thank you for submitting this report. You have helped make Perl better.
 
With the release of Perl 5.24.0 on May 9, 2016, this and 149 other issues have been resolved.

Perl 5.24.0 may be downloaded via https://metacpan.org/release/RJBS/perl-5.24.0