Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: ab4db5060c6d4e9b5e306d6cb51b86a05c036ae4
https://github.com/Perl/perl5/commit/ab4db5060c6d4e9b5e306d6cb51b86a05c036ae4
Author: Karl Williamson <[email protected]>
Date: 2026-09-19 (Sat, 19 Sep 2026)
Changed paths:
M regcomp.c
Log Message:
-----------
dump_regex_sets_structures: Display recursion level
This extra information can be useful in debugging
Commit: 56f69188c546e78fab6e617d80a448db0b5afff4
https://github.com/Perl/perl5/commit/56f69188c546e78fab6e617d80a448db0b5afff4
Author: Karl Williamson <[email protected]>
Date: 2026-09-19 (Sat, 19 Sep 2026)
Changed paths:
M embed.fnc
M embed.h
M proto.h
M regcomp.c
Log Message:
-----------
dump_regex_sets_structures() Add caller line number
This adds printing the caller line number to this debug routine. This
enables plunking down calls to it temporarily when actually doing
debugging and being able to distinguish between them with a minimum of
fuss.
Commit: a20f87cbe88716facf3ca9e4c3d161b3c0382707
https://github.com/Perl/perl5/commit/a20f87cbe88716facf3ca9e4c3d161b3c0382707
Author: Karl Williamson <[email protected]>
Date: 2026-09-19 (Sat, 19 Sep 2026)
Changed paths:
M regcomp.c
M t/re/reg_mesg.t
M t/re/regex_sets.t
Log Message:
-----------
regcomp: Don't parse ahead in sets recursion
Fixes #24238
This bug was introduced by
commit d8d1dede53afc4f33cf63203b0992459fe964dc3
Author: Karl Williamson <[email protected]>
Date: Mon Feb 17 12:07:07 2020 -0700
Improve handling of nested qr/(?[...])/
which changed how interpolated ("nested") sets expressions were handled.
The nesting is done by recursive calls then as now, but certain details
were changed by that commit
The current bug is due to getting the next character in the input at the
end of a nested call, and the layer above is not expecting that. The
solution is just to avoid getting that character when recursed.
However, this causes a different error message to be displayed than
prior to this commit in certain cases. The old message displayed was
Unexpected ']' with no following ')'
which is accurate. The new one is
Operand with no preceding operator
which is no less accurate. I considered making a special case to try to
avoid the diagnostic wording change, and I would have done so if this
were just a warning. But it is a fatal error, so I think it quite unlikely
that real code is expecting to not compile and to not compile with this
particular message. And I think the new message is a bit more to the
point of what is wrong, so is actually better than before.
Compare: https://github.com/Perl/perl5/compare/1e5751ae732b...a20f87cbe887
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications