Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 16e43efd81368f85ada6f2d40658b305d92ba57e
https://github.com/Perl/perl5/commit/16e43efd81368f85ada6f2d40658b305d92ba57e
Author: David Mitchell <da...@iabyn.com>
Date: 2022-07-09 (Sat, 09 Jul 2022)
Changed paths:
M pp_ctl.c
M t/re/pat_re_eval.t
Log Message:
-----------
fix another panic from eval {} inside /(?{...})/
GH #19390
This issue is similar to GH #19680 (fixed by v5.37.0-272-g5fd637ce8c),
but exiting the eval via a syntax error rather than via raising an
exception.
In this case, the NULL op_next of the OP_ENTEREVAL was passed to a new
RUNOPS loop, which would normally SEGV (or on debugging builds, warn
"NULL OP IN RUN").
Commit: a7304a688ff280f4bd0928e288e5541871ba0806
https://github.com/Perl/perl5/commit/a7304a688ff280f4bd0928e288e5541871ba0806
Author: David Mitchell <da...@iabyn.com>
Date: 2022-07-09 (Sat, 09 Jul 2022)
Changed paths:
M pp_ctl.c
Log Message:
-----------
fix typos in pp_ctl.c
some code comments I added recently kept referring to the function
do_catch() when it's actually docatch().
Compare: https://github.com/Perl/perl5/compare/284a9742c96b...a7304a688ff2
