Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: b33c0f81bde58bb7d2fa09ec850638ced3707218
https://github.com/Perl/perl5/commit/b33c0f81bde58bb7d2fa09ec850638ced3707218
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: White-space/comments only
Commit: d486815ba407757197591de7574ddf3b8006bba9
https://github.com/Perl/perl5/commit/d486815ba407757197591de7574ddf3b8006bba9
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Clarify code, add comment
Instead of omitting a parameter, explicitly mark it 'undef' for code
readability, and add a comment as to what this is all about.
Commit: 72af034b4040a04ff0c262dc9322a2c5ff51b7a6
https://github.com/Perl/perl5/commit/72af034b4040a04ff0c262dc9322a2c5ff51b7a6
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Mv line to avoid a pattern match
We've already done the match by the time of the new place
Commit: 6ca7d2f9611c64bc5d80c682ea8a0449d3fd659f
https://github.com/Perl/perl5/commit/6ca7d2f9611c64bc5d80c682ea8a0449d3fd659f
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M intrpvar.h
M regen/embed.pl
Log Message:
-----------
Fix up some intrpvar variable visibilities
Currently all PL_ variables are considered to be visible everywhere, but
a future commit will start to pay attention to their declared
visibilities (defaulting to always visible if no declaration).
This commit makes sure that will leave the visibilities as they
currently are by adding the ones declared to being hidden to the
unresolved override list. I also looked at a snapshot of metacpan for
any uses of these symbols, and if found, instead changed their
declarations to be always visible.
Commit: 232de31997605a70ab58e6d1e9765f2f14c65217
https://github.com/Perl/perl5/commit/232de31997605a70ab58e6d1e9765f2f14c65217
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Skip embedvar.h in calculating visibility
This header file is constructed by this program. It has nothing to
offer to the portions of the program that calculate symbol visibilities.
(Nothing in it indicates visibility) So, just skip it.
Commit: 9960f7afaf9b48248c371a573279f0c860ef7858
https://github.com/Perl/perl5/commit/9960f7afaf9b48248c371a573279f0c860ef7858
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Default Perl reserveds are always visible
Symbols like PL_foo should be considered to be visible to any module
wanting to use it, unless there is a declaration to the contrary.
Commit: eafb9b330d30edc169a90b120915e85aeaf2525b
https://github.com/Perl/perl5/commit/eafb9b330d30edc169a90b120915e85aeaf2525b
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Build up re's from smaller ones
I'm not sure this is worth bothering with, but this creates longer
string by adding to shorter one, and then constructs regex patterns from
the various steps.
Commit: 9a06cf093fd06a4aeca62586fac6ef5ada495467
https://github.com/Perl/perl5/commit/9a06cf093fd06a4aeca62586fac6ef5ada495467
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M regen/embed.pl
Log Message:
-----------
embed.pl: Keep track of input line number for debug
I found myself wanting to know exactly where something is in the files
read by this program.
Commit: 4d19083e232512321ce7008884296c2c0c0bf745
https://github.com/Perl/perl5/commit/4d19083e232512321ce7008884296c2c0c0bf745
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M embed.h
M regen/embed.pl
Log Message:
-----------
embed.pl: Get stored visibility if not explicit
We can have groups like
apidoc Am|foo
apidoc_item bar
...
This says the visibility of 'foo' is A (for all, or everywhere), and bar
inherits that. But we can also have groups like
apidoc foo
apidoc_item bar
where "foo's" visibility is defined elsewhere. For example, "foo" could
actually be a function, and its visibility defined in embed.fnc.
In the latter case, we've already parsed embed.fnc, and so likely know
the visibility of 'foo' and have stored it.
This commit looks at the place it would be stored and uses that if there
is no visibility specified here for 'foo'. This is somewhat cheating,
to know how the data structure is laid out, but it is the most
convenient way to do this, and I think, acceptable.
This single line change to the code pointed out several instances where
the ommission of this value led to not knowing what to do, so several
symbols were added to the override list that actually weren't a problem,
and so this commit removes them.
Commit: 278e3a0f241c7c119916a574a06a9ddd3e6e76d0
https://github.com/Perl/perl5/commit/278e3a0f241c7c119916a574a06a9ddd3e6e76d0
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M autodoc.pl
M embed.fnc
M intrpvar.h
M regen/embed.pl
Log Message:
-----------
Add 'apidoc-flag' to perlapi generation
This is designed to make noting what flag bits a function or macro takes
very easy, while helping downstream code that processes things do a
better job.
Commit: 6f673187e4234cd630e8a62b2283f2ffbbb9cc80
https://github.com/Perl/perl5/commit/6f673187e4234cd630e8a62b2283f2ffbbb9cc80
Author: Karl Williamson <[email protected]>
Date: 2026-01-27 (Tue, 27 Jan 2026)
Changed paths:
M cop.h
M dump.c
M gv.c
M hv.c
M inline.h
M intrpvar.h
M numeric.c
M op.c
M pad.c
M perl.c
M regen/embed.pl
M scope.c
M sv.c
M toke.c
M utf8.c
Log Message:
-----------
perlapi: Use new 'apidoc_flag' lines
This replaces the clumsy method used previously by the new construct
introduced in the previous commit.
There are many other potential places to use this new feature; this gets
just the important ones (the ones having separate apidoc entries for the
flags) and a few others that I tried. The others aren't important
currently, as the only current effect of adding them would be to add X<>
entries to perlapi; that could change. Devel::PPPort can be enhanced to
take advantage of these as well.
Compare: https://github.com/Perl/perl5/compare/3bad0ae11152...6f673187e423
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
