[ruby-core:75497] [Ruby trunk Bug#12376] No error for elseif condition

Issue #12376 has been updated by Daniel Ferreira.


Of course.
Makes perfect sense.
I would say the way to handle this bugs in a pro-active way would be to use 100% coverage in the test suite.
I can not see how the bug would be missed with that.
TDD as a must in ruby like always.
Thank you for the enlightenment Sirs.


----------------------------------------
Bug #12376: No error for elseif condition
https://bugs.ruby-lang.org/issues/12376#change-58614

* Author: Daniel Ferreira
* Status: Rejected
* Priority: Normal
* Assignee: 
* ruby -v: 2.3.0
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Something I have been for a long time wondering about.
I don't know if this is a parsing problem or not but for me it seems like it is.

Replication:

``` ruby
$ irb
> RUBY_VERSION
 => '2.3.0'
> a = 1
> if a == 2
>   puts 2
> elsif a == 3
>   puts 3
> elseif a == 1
>   puts 1
> else
>   puts 0
> end
0
 => nil
```

Shouldn't we have a parse error triggered here? 
We can replace *elseif* for any other instruction like *foo* for instance.

I believe this behaviour is around for a long time.



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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>