Re: [perl #120128] [PATCH] Optimise if(a || b) and unless(a && b)

On 8 October 2013 22:05, Matthew Horsfall <perlbug-followup@perl.org> wrote:
> # New Ticket Created by  Matthew Horsfall
> # Please include the string:  [perl #120128]
> # in the subject line of all future correspondence about this issue.
> # <URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=120128 >
>
>
> This is a bug report for perl from WolfSage@gmail.com,
> generated with the help of perlbug 1.39 running under perl 5.10.1.
>
>
> -----------------------------------------------------------------
> [Please describe your issue here]
>
> I've squashed the two prevous commits related to OP_AND/OP_OR/OP_DOR
> optimisations and attached it here, and removed the OP_OR/OP_DOR chaining
> since it was dead wrong.
>
> It broke this case:
>
>   $b = 0;
>
>   $x = $b // $c || 'cat';
>
> (It caused $x to be 0 instead of 'cat').

Wow. That that results in "cat" is quite surprising to me. Isn't that
a precedence bug?

Yves

• [perl #120128] [PATCH] Optimise if(a || b) and unless(a && b) by Matthew Horsfall
• Re: [perl #120128] [PATCH] Optimise if(a || b) and unless(a && b) by demerphq
• Re: [perl #120128] [PATCH] Optimise if(a || b) and unless(a && b) by Paul Johnson
• Re: [perl #120128] [PATCH] Optimise if(a || b) and unless(a && b) by demerphq