[#75687] [Ruby trunk Bug#12416] struct rb_id_table lacks mark function — shyouhei@...
Issue #12416 has been reported by Shyouhei Urabe.
3 messages
2016/05/23
[#75763] [Ruby trunk Feature#12435] Using connect_nonblock to open TCP connections in Net::HTTP#connect — mohamed.m.m.hafez@...
Issue #12435 has been reported by Mohamed Hafez.
3 messages
2016/05/28
[#75774] Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock — Mohamed Hafez <mohamed.m.m.hafez@...>
Hi all, every now and then in my production server, I'm
4 messages
2016/05/30
[#75775] Re: Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock
— Mohamed Hafez <mohamed.m.m.hafez@...>
2016/05/30
Or does MRI's OpenSSL::SSL::SSLSocket#connect_nonblock just return
[#75782] Important: Somewhat backwards-incompatible change (Fwd: [ruby-cvs:62388] duerst:r55225 (trunk): * string.c: Activate full Unicode case mapping for UTF-8) — Martin J. Dürst <duerst@...>
With the change below, I have activated full Unicode case mapping for
4 messages
2016/05/31
[ruby-core:75493] [Ruby trunk Bug#12376] No error for elseif condition
From:
zverok.offline@...
Date:
2016-05-13 10:59:36 UTC
List:
ruby-core #75493
Issue #12376 has been updated by Victor Shepelev. It is parsed as ~~~ruby if a == 2 puts 2 elsif a == 3 puts 3 elseif(a == 1) puts 1 else puts 4 end ~~~ With `elseif` being just a method call. With this branch not evaluated, there is no problem with unknown method in it. ---------------------------------------- Bug #12376: No error for elseif condition https://bugs.ruby-lang.org/issues/12376#change-58610 * Author: Daniel Ferreira * Status: Open * 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:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>