[Perl/perl5] 943f7e: bisect-runner docs: wording and pod fixups

2023-01-18 Thread Hugo van der Sanden via perl5-changes
  Branch: refs/heads/gh20724
  Home:   https://github.com/Perl/perl5
  Commit: 943f7e554a81aed564f801e94c0af01fafda54b6
  
https://github.com/Perl/perl5/commit/943f7e554a81aed564f801e94c0af01fafda54b6
  Author: Hugo van der Sanden 
  Date:   2023-01-19 (Thu, 19 Jan 2023)

  Changed paths:
M Porting/bisect-runner.pl

  Log Message:
  ---
  bisect-runner docs: wording and pod fixups




[Perl/perl5] 1a9750: bisect-runner docs: modify example to use 'expect-...

2023-01-18 Thread Hugo van der Sanden via perl5-changes
  Branch: refs/heads/gh20724
  Home:   https://github.com/Perl/perl5
  Commit: 1a9750d4de213f0731b064de4f4bf054877227df
  
https://github.com/Perl/perl5/commit/1a9750d4de213f0731b064de4f4bf054877227df
  Author: Hugo van der Sanden 
  Date:   2023-01-18 (Wed, 18 Jan 2023)

  Changed paths:
M Porting/bisect-runner.pl

  Log Message:
  ---
  bisect-runner docs: modify example to use 'expect-fail'


  Commit: de5ceda9ecdd59d44ed4e9a8c14411261d31f61b
  
https://github.com/Perl/perl5/commit/de5ceda9ecdd59d44ed4e9a8c14411261d31f61b
  Author: Hugo van der Sanden 
  Date:   2023-01-19 (Thu, 19 Jan 2023)

  Changed paths:
M Porting/bisect-runner.pl

  Log Message:
  ---
  bisect-runner docs: explain more about bisection


Compare: https://github.com/Perl/perl5/compare/1a9750d4de21%5E...de5ceda9ecdd


[Perl/perl5] 09b3a4: op/fork.t: skip the ulimit fork test under LSAN

2023-01-18 Thread Tony Cook via perl5-changes
  Branch: refs/heads/blead
  Home:   https://github.com/Perl/perl5
  Commit: 09b3a407e87f128d7aecd14f9c8d75dcff9aaaf8
  
https://github.com/Perl/perl5/commit/09b3a407e87f128d7aecd14f9c8d75dcff9aaaf8
  Author: Tony Cook 
  Date:   2023-01-19 (Thu, 19 Jan 2023)

  Changed paths:
M t/op/fork.t

  Log Message:
  ---
  op/fork.t: skip the ulimit fork test under LSAN

This was producing noise, at least on Linux, since the -u limit on
Linux also limits threads.

Fixes #20712




[Perl/perl5] dc030d: regcomp.c - add optimistic eval (*{ ... }) and (**...

2023-01-18 Thread Yves Orton via perl5-changes
  Branch: refs/heads/yves/optimistic_eval
  Home:   https://github.com/Perl/perl5
  Commit: dc030d62b92c1ddba368b824fcea7c88c178cb35
  
https://github.com/Perl/perl5/commit/dc030d62b92c1ddba368b824fcea7c88c178cb35
  Author: Yves Orton 
  Date:   2023-01-18 (Wed, 18 Jan 2023)

  Changed paths:
M pod/perldelta.pod
M pod/perlre.pod
M regcomp.c
M regcomp.h
M regcomp_debug.c
M regcomp_internal.h
M regcomp_study.c
M regexec.c
M regnodes.h
M t/re/pat_re_eval.t
M t/re/pat_rt_report.t
M toke.c

  Log Message:
  ---
  regcomp.c - add optimistic eval (*{ ... }) and (**{ ... })

This adds (*{ ... }) and (**{ ... }) as equivalents to (?{ ... }) and
(??{ ... }). The only difference being that the star variants are
"optimisitic" and are defined to never disable optimisations. This is
especially relevant now that use of (?{ ... }) prevents important
optimisations anywhere in the pattern, instead of the older and inconsistent
rules where it only affected the parts that contained the EVAL.

It is also very useful for injecting debugging style expressions to the
pattern to understand what the regex engine is actually doing. The older
style (?{ ... }) variants would change the regex engines behavior, meaning
this was not as effective a tool as it could have been.

Similarly it is now possible to test that a given regex optimisation
works correctly using (*{ ... }), which was not possible with (?{ ... }).