Issue #10947 has been updated by Sam Davies.


Jeremy Evans wrote:
> 
> This is valid syntax.  ruby parses this as:
> 
> ~~~
> if (false && false && false; true)
> ~~~
> 
> This is expected behavior, and changing how ruby handles this would break working code.

Ah I see, so Ruby interprets the newline as ;. Thanks, I'll watch out for this more carefully in future.

I guess this issue can be closed.

----------------------------------------
Bug #10947: Multiline if statement returns unexpected value instead of raising a syntax error
https://bugs.ruby-lang.org/issues/10947#change-51798

* Author: Sam Davies
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: 2.1.2
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
Here is an invalid multiline if statement

if (false &&
    false &&
    false
    true)
    puts "I was expecting an exception but saw this message instead"
end

As far as I can tell this is and should never be interpreted as valid syntax.

What actually happens is instead of raising an exception, ruby ignores all values except the last and only evaluates that. If you forget a && at the end of a line this can result in very unexpected behavior.



-- 
https://bugs.ruby-lang.org/