Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 2aa73c643cc3dde35932f5e6209f50ca2f28fc93
https://github.com/Perl/perl5/commit/2aa73c643cc3dde35932f5e6209f50ca2f28fc93
Author: Karl Williamson <[email protected]>
Date: 2022-07-01 (Fri, 01 Jul 2022)
Changed paths:
M autodoc.pl
Log Message:
-----------
perlapi: Ensure ref-only items have X<>
Some minor API elements, such as flag values, in perlapi are mentioned
only in passing in the pod of some encompassing element.
This commit makes sure those minor elements have a X<> pod element
generated for them in the appropriate place. This makes sure that other
code that, say, indexes the API knows whereabouts to link, etc. to.
Commit: cda0e7fb7b98e695b739b9b364a1b0522105a86d
https://github.com/Perl/perl5/commit/cda0e7fb7b98e695b739b9b364a1b0522105a86d
Author: Karl Williamson <[email protected]>
Date: 2022-07-01 (Fri, 01 Jul 2022)
Changed paths:
M autodoc.pl
Log Message:
-----------
perlapi,intern: Split undcmntd items into 3 classes
Those classes being: plain, experimental, and deprecated.
Suppose I'm an XS writer and I've found an undocumented function or
macro that I'd like to use. Should I use it?
Certainly not if it's deprecated.
Pretty iffy if it's experimental, but maybe worth a try to ask p5p about
it.
Less iffy if just plain, but the pod says to ask p5p to be sure.
These distinctions do matter some, and so this commit makes them. Prior
to it, perlapi experimental and deprecated elements weren't mentioned
anywhere, as if they had dropped off the face of the earth.
Commit: c5321c9615e8ff5e65c601de5fd409878da8568b
https://github.com/Perl/perl5/commit/c5321c9615e8ff5e65c601de5fd409878da8568b
Author: Karl Williamson <[email protected]>
Date: 2022-07-01 (Fri, 01 Jul 2022)
Changed paths:
M autodoc.pl
Log Message:
-----------
perlapi: Slight wording change
Compare: https://github.com/Perl/perl5/compare/855c15d32d2f...c5321c9615e8
