On Wed, Sep 19, 2012 at 8:00 AM, Damjan Rems <[email protected]> wrote:
> So there is a good reason not to implement object duplication (deep > cloning). Results may be unpredictable so better don't do it. As I said elsewhere: I prefer custom logic tailored to the use case and not a general mechanism which simply does a deep copy. That's likely more efficient and less error prone than the deep copying approach. > Although I never liked the argument if it is good for them than it is > good for us. I am not sure I understand what you mean here. Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- You received this message because you are subscribed to the Google Groups ruby-talk-google group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/ruby-talk-google?hl=en
