From: Yukihiro Matsumoto <matz@...>
Date: 2012-04-02T00:25:05+09:00
Subject: [ruby-core:44041] Re: [Ruby 1.8 - Bug #6239] super Does Not Pass Modified Rest Args When Originally Empty

Hi,

It has not been considered as a bug.  The old document described this
behavior.  Ko1 asked me to allow behavioral change in 1.9, and I admit.

							matz.

In message "Re: [ruby-core:44023] [Ruby 1.8 - Bug #6239] super Does Not Pass Modified Rest Args When Originally Empty"
    on Sun, 1 Apr 2012 03:20:18 +0900, "marcandre (Marc-Andre Lafortune)" <ruby-core@marc-andre.ca> writes:

|matz (Yukihiro Matsumoto) wrote:
|> It's behavior change in 1.9, and we are not going to change the behavior in 1.8 (other than fixing bugs) any more.
|
|Oh, it is?
|
|So you mean that it was a known fact that there was an exceptional case with super and modified rest argument only when that rest argument was empty? And that it was a "feature"? Was there any rationale for that behavior?
|
|I'm not saying the bug must be fixed, as it can be easily circumvented using explicit arguments, but it definitely looks like a bug to me.