Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: a61bf5550e2d24d20d8d124241983a1c8c49d024
https://github.com/Perl/perl5/commit/a61bf5550e2d24d20d8d124241983a1c8c49d024
Author: TAKAI Kousuke <[email protected]>
Date: 2025-11-20 (Thu, 20 Nov 2025)
Changed paths:
M sv.h
Log Message:
-----------
sv.h: Make SvIsUV() return 1 (rather than 0x80000000) for true condition
This would make it easier to receive the result with `bool` type.
Note that (implicit) casting to C99 `_Bool` automatically converts
any nonzero scalar values to 1, so that this change is technically
not necessary in C99 which perl now requires to compile. But I think
it will keep the code less surprising.
Commit: e721750ea2bfe6dca77db907980ae473a073ebbf
https://github.com/Perl/perl5/commit/e721750ea2bfe6dca77db907980ae473a073ebbf
Author: TAKAI Kousuke <[email protected]>
Date: 2025-11-20 (Thu, 20 Nov 2025)
Changed paths:
M pp.c
M pp_hot.c
Log Message:
-----------
pp.c, pp_hot.c: Use SvIsUV rather than SvUOK after SvIV_please_nomg
SvUOK(x) inside a block guarded by SvIV_please_nomg(x) can be
replaced by SvIsUV(x) because SvIV_please_nomg implies SvIOK.
This will save a few code size and runtime CPU cycles, because
many CPUs can do single-bit tests like SvIsUV in fewer instructions
than multi-bit tests like SvUOK.
Commit: 4f5c042cd57511863ed6ec92f90b776f0a894b6b
https://github.com/Perl/perl5/commit/4f5c042cd57511863ed6ec92f90b776f0a894b6b
Author: TAKAI Kousuke <[email protected]>
Date: 2025-11-20 (Thu, 20 Nov 2025)
Changed paths:
M hv.c
Log Message:
-----------
hv.c: Use SvIsUV instead of SvUOK in the block where SvIOK holds true.
Because SvUOK is essentially (SvIOK && SvIsUV), SvUOK is redundant
in the block where SvIOK is guaranteed to hold true.
Compare: https://github.com/Perl/perl5/compare/5cc1154cbc58...4f5c042cd575
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
