summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
9065925)
with commit v5.25.8-172-gb243b19, I removed some special-casing of the A
in (A&&B) being in boolean context, but forgot to remove a comment
describing this special-casing.
# sub f { ....; ((%h || $x) || $y)) }
# If f() is called in void context, then %h can return a boolean value;
# if in scalar context, %h must return a key count.
# sub f { ....; ((%h || $x) || $y)) }
# If f() is called in void context, then %h can return a boolean value;
# if in scalar context, %h must return a key count.
-#
-# With (op && other), its ok to treat op as in bool cxt even when the &&
-# is in scalar cxt, as long as whatever op returns as a false boolean value
-# matches what it returns as a false scalar value (IV(0) in the case of
-# rv2hv etc). This is because in (A && B), A is returned only when A is
-# false.
for my $ops (
# op code op path flag maybe flag
for my $ops (
# op code op path flag maybe flag