Maintaining Perl (Tony Cook) November 2025
Wed, 10-Dec-2025 by
alh
edit post
Tony write:
```
In addition to the typical stream of small changes to review, Dave's
second AST rebuild of ExtUtils::ParseXS arrived (#23883), and I spent
several hours reviewing it.
In response to #23918 I worked on adding numeric comparison APIs,
which are complicated by overloading, NaNs, SVs dual IV/NV
implmentation, and of course by overloading. This includes some fixes
for the existing sv_numeq() API. You can see the current state of
this work in #23966.
[Hours] [Activity]
2025/11/03 Monday
0.37 #23886 review and approve
0.22 #23873 review other comments and follow-up
0.47 #23887 review, research and approve
1.72 #23890 review, testing
0.23 #23890 comment
0.08 #23891 review and approve
0.18 #23895 review and approve
0.67 #23896 review and comment
=====
3.94
2025/11/04 Tuesday
0.57 coverity scan results, testing, comment on #23871
1.15 #23885 review and comment
1.03 #23871 testing per wolfsage’s example, work on a
regression test and fix, testing, push to PR 23897
1.67 #21877 debugging, fix my understanding on PerlIO and the
code, testing
=====
4.42
2025/11/05 Wednesday
0.70 #23897 fix non-taint perl, testing and update PR
0.58 #23896 recheck
1.50 #23885 comment
0.57 #21877 look into remaining test failure, find the cause
and workaround it
=====
3.35
2025/11/06 Thursday
0.08 #23902 review and approve
0.08 #23898 review and approve
0.55 #23899 review and approve
0.97 #23901 review and approve
0.95 #23883 review
1.40 #23883 review up to Node::include
=====
4.03
2025/11/10 Monday
1.60 #23795 review updates, comment
0.35 #23907 review, research and approve
1.07 #23908 review, research, comment (fixed while I worked)
0.63 #23883 continue review, comment
=====
3.65
2025/11/11 Tuesday
0.57 #23908 review updates and approve
0.40 #23911 review, review history of associated ticket and
approve
0.85 #23883 more review
1.37 #23883 more review
=====
3.19
2025/11/12 Wednesday
0.73 #23913 review, research and approve
0.77 #23914 review, check for SvIsUV() usage on CPAN
0.83 #23910 testing, get some strange results
0.82 #23910 debugging, can’t reproduce in new builds
0.67 #23883 more review
=====
3.82
2025/11/13 Thursday
0.73 #23918 review discussion and research
0.75 #23917 review and approve
0.23 #23919 review and approve
1.03 #23883 more review
1.27 #23883 more review
=====
4.01
2025/11/17 Monday
1.13 testing, comments on new XS API list thread
0.97 #23923 review and approve
1.25 #23914 testing, comment, review
0.43 #23914 more review and approve
0.93 #23888 review, comments, some side discussion of 23921
=====
4.71
2025/11/18 Tuesday
0.50 #23888 review updates, testing,approve
0.27 #23943 review and approve
0.52 #23883 more review
1.27 #23883 more review
=====
2.56
2025/11/19 Wednesday
0.78 #23922 review and approve
1.08 #23918 work on new compare APIs
0.53 #23918 debugging
1.22 #23918 testing, cleanup
0.82 #23918 re-work documentation
=====
4.43
2025/11/20 Thursday
2.50 #23918 work on sv_numcmp(), research, test code, testing,
debugging
1.07 #23918 work out an issue, more testing, document sv_numcmp
variants
=====
3.57
2025/11/24 Monday
0.08 #23819 review and approve
2.77 #23918 NULL tests and fix, test for NV/IV mishandling and
fix
0.82 #23918 open #23956, start on le lt ge gt implementation
1.20 #23918 finish implementation, test code, testing
=====
4.87
2025/11/25 Tuesday
0.67 #23885 review, comment
1.13 #23885 more review
1.03 #23918 some polish
=====
2.83
2025/11/26 Wednesday
0.07 #23960 review and approve
2.07 #23885 review, research and comments
0.48 #23918 more polish, testing
1.60 #23918 finish polish, push for CI
=====
4.22
2025/11/27 Thursday
0.58 #23918 check CI, add perldelta and push
0.58 check CI results and make PR 23966
0.48 comment on dist discussion on list
=====
1.64
2025/11/28 Friday
0.18 #23918 fix a minor issue
=====
0.18
Which I calculate is 59.42 hours.
Approximately 32 tickets were reviewed or worked on.
```
Comments (0)