In perl.git, the branch smoke-me/coresubs has been created
<http://perl5.git.perl.org/perl.git/commitdiff/4d7f76092fbbb7a97548d985f52fcf28b46b3f4c?hp=0000000000000000000000000000000000000000>
at 4d7f76092fbbb7a97548d985f52fcf28b46b3f4c (commit)
- Log -----------------------------------------------------------------
commit 4d7f76092fbbb7a97548d985f52fcf28b46b3f4c
Author: Father Chrysostomos <[email protected]>
Date: Tue May 17 00:27:30 2016 -0700
Allow &CORE::foo() with array functions
M gv.c
M pp.c
M t/op/coreamp.t
commit 95faa7716f076b05914c1b14a96304a79f48eeac
Author: Father Chrysostomos <[email protected]>
Date: Mon May 16 23:32:06 2016 -0700
perldiag: Document unknown OA_* panic
M pod/perldiag.pod
commit 40b6ba1cf9b1bd8c37e9885b8d3aaf118299059e
Author: Father Chrysostomos <[email protected]>
Date: Mon May 16 23:10:17 2016 -0700
Allow &CORE::foo() with hash functions
&CORE::keys does not yet work as an lvalue. (Iâm not sure how to make
that work.)
M doop.c
M gv.c
M lib/B/Op_private.pm
M op.c
M pp.c
M regen/op_private
M t/op/coreamp.t
commit b2ffeb26f323a3bcaaa13620f67dbb2dbd7dde57
Author: Father Chrysostomos <[email protected]>
Date: Mon May 16 18:16:28 2016 -0700
Increase $Opcode::VERSION to 1.35
M ext/Opcode/Opcode.pm
commit 1d7fa4707f92de7dd2c34efd1e8bf5d31f023fe5
Author: Father Chrysostomos <[email protected]>
Date: Mon May 16 18:15:42 2016 -0700
Add avhvswitch op
&CORE::keys() et al. will use this to switch between keys and akeys
depending on the argument type.
M ext/Opcode/Opcode.pm
M lib/B/Op_private.pm
M opcode.h
M opnames.h
M pp.c
M pp_proto.h
M regen/opcodes
commit 2c0aee6bc5c5252c814c536c7271afa49c41378e
Author: Father Chrysostomos <[email protected]>
Date: Mon May 16 18:09:02 2016 -0700
regen/opcodes: Re-order aeach, akeys, and avalues
In a forthcoming commit, I will need them to be in the same order as
the corresponding hash functions.
M opcode.h
M opnames.h
M regen/opcodes
commit 7e4eea0f9875d782e438028ca9a66a0da92e5936
Author: Father Chrysostomos <[email protected]>
Date: Sun May 15 13:59:24 2016 -0700
pp.c: Use PL_op_desc in pp_coreargs
OP_DESC is inconvienient here, because it expects an op, not an op
number, so we have to follow pointers to find an appropriate op. It
is also needlessly expensive, since we do not need to check for custom
ops in pp_coreargs (which OP_DESC does). Just access the underlying
array directly.
M pp.c
-----------------------------------------------------------------------
--
Perl5 Master Repository