https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112012-04-01T02:51:06ZRuby Issue Tracking SystemRuby 1.8 - Bug #6239: super Does Not Pass Modified Rest Args When Originally Emptyhttps://bugs.ruby-lang.org/issues/6239?journal_id=255472012-04-01T02:51:06Zmudge (Paul Mucur)mudge@mudge.name
<ul></ul><p>As a side note, both JRuby 1.6.6 and Rubinius 1.2.4 in 1.8 compatibility mode follow the behaviour of 1.9.2.</p>
<p>James Hunt and I have filed a pull request to the RubySpec project to document this issue at: <a href="https://github.com/rubyspec/rubyspec/pull/130" class="external">https://github.com/rubyspec/rubyspec/pull/130</a></p> Ruby 1.8 - Bug #6239: super Does Not Pass Modified Rest Args When Originally Emptyhttps://bugs.ruby-lang.org/issues/6239?journal_id=255492012-04-01T02:57:48Zmatz (Yukihiro Matsumoto)matz@ruby.or.jp
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Rejected</i></li></ul><p>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.</p>
<p>Matz.</p> Ruby 1.8 - Bug #6239: super Does Not Pass Modified Rest Args When Originally Emptyhttps://bugs.ruby-lang.org/issues/6239?journal_id=255512012-04-01T03:20:16Zmarcandre (Marc-Andre Lafortune)marcandre-ruby-core@marc-andre.ca
<ul></ul><p>Hi Matz</p>
<p>matz (Yukihiro Matsumoto) wrote:</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>Oh, it is?</p>
<p>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?</p>
<p>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.</p> Ruby 1.8 - Bug #6239: super Does Not Pass Modified Rest Args When Originally Emptyhttps://bugs.ruby-lang.org/issues/6239?journal_id=255692012-04-02T00:29:13Zmatz (Yukihiro Matsumoto)matz@ruby.or.jp
<ul></ul><p>Hi,</p>
<p>It has not been considered as a bug. The old document described this<br>
behavior. Ko1 asked me to allow behavioral change in 1.9, and I admit.</p>
<pre><code> matz.
</code></pre>
<p>In message "Re: <a href="/issues/6239">[ruby-core:44023]</a> [Ruby 1.8 - Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: super Does Not Pass Modified Rest Args When Originally Empty (Rejected)" href="https://bugs.ruby-lang.org/issues/6239">#6239</a>] super Does Not Pass Modified Rest Args When Originally Empty"<br>
on Sun, 1 Apr 2012 03:20:18 +0900, "marcandre (Marc-Andre Lafortune)" <a href="mailto:ruby-core@marc-andre.ca" class="email">ruby-core@marc-andre.ca</a> writes:</p>
<p>|matz (Yukihiro Matsumoto) wrote:<br>
|> 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.<br>
|<br>
|Oh, it is?<br>
|<br>
|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?<br>
|<br>
|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.</p> Ruby 1.8 - Bug #6239: super Does Not Pass Modified Rest Args When Originally Emptyhttps://bugs.ruby-lang.org/issues/6239?journal_id=255942012-04-02T18:43:11Zmudge (Paul Mucur)mudge@mudge.name
<ul></ul><p>Thank you, Matz.</p>
<p>We have now covered this behaviour in RubySpec as of <a href="https://github.com/rubyspec/rubyspec/commit/ffb634f3899dfc0d8a494afa8c754992041ddb2e" class="external">https://github.com/rubyspec/rubyspec/commit/ffb634f3899dfc0d8a494afa8c754992041ddb2e</a></p>