Branch: refs/heads/blead Home: https://github.com/Perl/perl5 Commit: 06eefcf66c36fa1ea44357002ed1c9dbf7354734 https://github.com/Perl/perl5/commit/06eefcf66c36fa1ea44357002ed1c9dbf7354734 Author: Paul "LeoNerd" Evans <leon...@leonerd.org.uk> Date: 2025-08-14 (Thu, 14 Aug 2025)
Changed paths: M class.c M lib/B/Op_private.pm M opcode.h M regen/op_private Log Message: ----------- Define OPpSELF_IN_PAD private flag to OP_METHSTART This flag indicates that `$self` argument handling has already been performed by the subroutine signature, so it should find the value already in the pad. Commit: 4b060dfa9717f7225c2029c9f4eca50c9bcb04b7 https://github.com/Perl/perl5/commit/4b060dfa9717f7225c2029c9f4eca50c9bcb04b7 Author: Paul "LeoNerd" Evans <leon...@leonerd.org.uk> Date: 2025-08-14 (Thu, 14 Aug 2025) Changed paths: M embed.fnc M embed.h M op.c M proto.h Log Message: ----------- Add a subsignature_append_fence_op() A "fence op" is a miscellaneous op fragment that performs some work for side-effects during processing of a subroutine signature. In terms of timing, it will run at some time after any previously-defined arguments have been assigned from argument values passed in by the caller, but before any defaulting expressions for parameters that come after it are run. We specifically make no guarantees about whether parameters defined after this op have had their values assigned, nor whether defaulting expressions of earlier parameters have already been invoked. This is intentional because upcoming changes will change the order of these. The intention here is that method subroutines will use a fence op for the `OP_METHSTART` behaviour, ensuring that subsequent defaulting expressions can see the values of field bindings established by processing the `$self` parameter. Commit: b1f152e440e8f9f3b58c99c2c373a4fb04d2b1c2 https://github.com/Perl/perl5/commit/b1f152e440e8f9f3b58c99c2c373a4fb04d2b1c2 Author: Paul "LeoNerd" Evans <leon...@leonerd.org.uk> Date: 2025-08-14 (Thu, 14 Aug 2025) Changed paths: M class.c M lib/B/Deparse.pm M op.c M pod/perldelta.pod M t/class/accessor.t M t/class/method.t Log Message: ----------- Process `$self` in method subs as a subsignature parameter This has at least three advantages: * Removes more special-case code from `class.c` and makes generated optrees more similar to others * Ensures that no other ops appear in the optree before signature handling (as the OP_METHSTART used to). This will be useful for upcoming faster-signatures changes * Corrects the previous "off-by-one" error in parameter counts as reported by the argument count check exception messages Compare: https://github.com/Perl/perl5/compare/23bbe7420f60...b1f152e440e8 To unsubscribe from these emails, change your notification settings at https://github.com/Perl/perl5/settings/notifications