[#24105] [Bug #1711] Marshal Failing to Round-Trip Certain Recurisve Data Structures — Run Paint Run Run <redmine@...>

Bug #1711: Marshal Failing to Round-Trip Certain Recurisve Data Structures

9 messages 2009/07/01

[#24116] [Bug #1715] Numeric#arg for NaN is Inconsistent Across Versions — Run Paint Run Run <redmine@...>

Bug #1715: Numeric#arg for NaN is Inconsistent Across Versions

10 messages 2009/07/02

[#24240] [Bug #1755] IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8 — Run Paint Run Run <redmine@...>

Bug #1755: IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8

8 messages 2009/07/09

[#24321] [Bug #1773] Gem path doesn't honor user gem? — Lin Jen-Shin <redmine@...>

Bug #1773: Gem path doesn't honor user gem?

12 messages 2009/07/14

[#24390] [Feature #1784] More encoding (Big5 series) support? — Lin Jen-Shin <redmine@...>

Feature #1784: More encoding (Big5 series) support?

12 messages 2009/07/16

[#24467] Re: [ruby-cvs:31226] Ruby:r24008 (ruby_1_8_6): Removed private on to_date and to_datetime. — Urabe Shyouhei <shyouhei@...>

Hello.

10 messages 2009/07/21

[#24472] [Feature #1800] rubygems can replace system executable files — Kazuhiro NISHIYAMA <redmine@...>

Feature #1800: rubygems can replace system executable files

13 messages 2009/07/21

[#24530] [Feature #1811] Default BasicSocket.do_not_reverse_lookup to true — Roger Pack <redmine@...>

Feature #1811: Default BasicSocket.do_not_reverse_lookup to true

9 messages 2009/07/23

[#24624] [Bug #1844] Immediates Should Not Respond to :dup — Run Paint Run Run <redmine@...>

Bug #1844: Immediates Should Not Respond to :dup

15 messages 2009/07/30

[ruby-core:24636] Re: [Bug #1844] Immediates Should Not Respond to :dup

From: Tomas Matousek <Tomas.Matousek@...>
Date: 2009-07-31 01:18:57 UTC
List: ruby-core #24636
What about adding Kernel#dup? method that is an alias of Kernel#dup: a clas=
s that cannot be duplicated would implement dup that throws an exception an=
d dup? that returns nil or self?

Tomas

-----Original Message-----
From: David A. Black [mailto:dblack@rubypal.com]
Sent: Thursday, July 30, 2009 6:10 PM
To: ruby-core@ruby-lang.org
Subject: [ruby-core:24635] Re: [Bug #1844] Immediates Should Not Respond to=
 :dup

Hi --

On Fri, 31 Jul 2009, Shyouhei Urabe wrote:

> Issue #1844 has been updated by Shyouhei Urabe.
>
>
> Anyway when getting back to :dup story, I'm not against to make it
> more "reliable".  But there seems to be several menu here:
>
> * respond_to?(:dup) to be false and calling dup to raise exception.
> Runpaint's original suggestion.
> * respond_to?(:dup) to be true and dup to return self. Jeremy's idea.

My own difficulty with Jeremy's idea is that 1 isn't a duplicate of 1.
In general, if x.dup returns x, it's not returning a duplicate of x, so the=
 method name becomes problematic.

In other words, I'm not sure about having dup be a no-op. On the other hand=
, I would very much *not* like to start seeing #respond_to? every time dup =
is used.


David

--
David A. Black / Ruby Power and Light, LLC / http://www.rubypal.com
Q: What's the best way to get a really solid knowledge of Ruby?
A: Come to our Ruby training in Edison, New Jersey, September 14-17!
    Instructors: David A. Black and Erik Kastner
    More info and registration: http://rubyurl.com/vmzN



In This Thread