Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 8f445452f05520d229d03e530ef88047142d6f9c
https://github.com/Perl/perl5/commit/8f445452f05520d229d03e530ef88047142d6f9c
Author: Karl Williamson <[email protected]>
Date: 2026-02-02 (Mon, 02 Feb 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Reorder a list; add comments
Naming a symbol with a trailing underscore indicates an intent for that
symbol to not be used directly by XS code. Separating those from the
other symbols highlights this.
Commit: 468d12e16f63d24facbe3e0a22e701a5807db563
https://github.com/Perl/perl5/commit/468d12e16f63d24facbe3e0a22e701a5807db563
Author: Karl Williamson <[email protected]>
Date: 2026-02-02 (Mon, 02 Feb 2026)
Changed paths:
M embed.h
M regen/embed.pl
Log Message:
-----------
embed.pl: RXf_PMf_ symbols should be visible everywhere
Fixes #24153; Fixes #24154
The spelling of various symbols changed in 5.43, to align with the C
Standard. That meant that any code using the old symbol, and which
didn't get updated, would break. Macros that used the old symbol were
updated to use the new one. Since we didn't get breakage, that meant
there was no tested code that used the old spelling directly.
When I was backporting the hardening of visibility to the beginning of
5.43, I found the spelling changes. If I didn't find a macro that used
the new spelling, I concluded that this symbol wasn't used in CPAN, even
indirectly. (I grepped a snapshot of metacpan to rule out direct
mentions.)
For the symbols that broke here, I did find indirect uses, but it
appeared to me that these were only uses by Perl extensions. I was
clearly wrong.
This fact indicates that we can resolve these symbols; they are needed
to be visible everywhere. There's three ways to resolve such things:
1. Document them. I don't see any real need for code beyond the already
existing code from needing to use them. Their use is obvious once
you see the pattern, so I don't see a need for them to even be put
in perlintern.
2. Change their names to begin with Perl_. This might be something to
do at a later date, but not in the 5.43 cycle.
3. Put them on the resolved list. I've opted for that now.
Compare: https://github.com/Perl/perl5/compare/9219dc2f15af...468d12e16f63
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
