[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>

I would like to request developers meeting around April 17 or 18 in this month.

14 messages 2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014 — Urabe Shyouhei <shyouhei@...> 2014/04/03

It's good if we have a meeting then.

[#61826] Re: Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...> 2014/04/03

Regarding openssl issues, I’ve discussed possible meeting time with Martin last month and he seemed positive.

[#61833] Re: Plan Developers Meeting Japan April 2014 — Martin Bo煬et <martin.bosslet@...> 2014/04/03

Hi,

[ruby-core:62245] [ruby-trunk - Bug #9475] Behavior change with include + super + alias_method between 1.9.x and 2.x

From: usa@...
Date: 2014-04-30 07:27:19 UTC
List: ruby-core #62245
Issue #9475 has been updated by Usaku NAKAMURA.

Backport changed from 1.9.3: DONTNEED, 2.0.0: REQUIRED, 2.1: REQUIRED to 1.9.3: DONTNEED, 2.0.0: DONE, 2.1: REQUIRED

backported r45367, r45387, r45388 and r45389 into ruby_2_0_0 at r45750.

----------------------------------------
Bug #9475: Behavior change with include + super + alias_method between 1.9.x and 2.x 
https://bugs.ruby-lang.org/issues/9475#change-46396

* Author: Ben Weintraub
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: 
* Target version: 
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin12.0]
* Backport: 1.9.3: DONTNEED, 2.0.0: DONE, 2.1: REQUIRED
----------------------------------------
Ruby 2.0 appears to have introduced a subtle behavior change in method resolution that persists in 2.1.0.

The attached test case (also visible online at https://gist.github.com/benweint/8791007) is extracted from an actual application, and while I won't defend the need to do something like this, it is clear that the behavior changed in 2.0. Note that this sounds similar to https://bugs.ruby-lang.org/issues/9236 but is in fact distinct - the test case given in that bug was fixed in Ruby 2.1.

Steps to reproduce:
1. Run the attached testcase on Ruby 1.9.3 note the output
2. Run the attached testcase on Ruby 2.0.0-p353 or 2.1.0-p0, and note the output

Expected results:
While it's certainly not obvious to me what 'should' happen when executing this code, on 1.9.3, it produces this output:

~~~
foo from C
foo from B
foo from A  
~~~

Actual results:
On 2.0+, I get this instead

~~~
foo from C
foo from B
foo from B (again)
foo from B
foo from B (again)
foo from B
... previous two lines repeated many times ...
test.rb:11: stack level too deep (SystemStackError)
~~~

That is to say, on 2.0, we get into an infinitely recursive loop that doesn't happen with 1.9.3.

---Files--------------------------------
test.rb (340 Bytes)


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

In This Thread

Prev Next