I'm going to briefly be a wise-guy to a (well intentioned) purpose. You appear to be suggesting that we call #deepCopy something else, and then fix it.
One might drag the fix into #deepCopy?? But years ago now, #deepCopy fell from grace, perhaps for good reason. What I recall seeing in its place was #postCopy that can be overriden to ensure a distinct copy; that seemed to be in contrast to #shallowCopy. This deserves some attention to ensure that we do the correct thing. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of arnaud Jean Baptiste Sent: Tuesday, October 20, 2009 10:07 AM To: Pharo Development Subject: [Pharo-project] Question about deepCopy, question: deepCopy have this behavior : - copy self. - then send deepCopy on all instance var. this behavior, make infinite loop when a object have instance variable which reference to himself or more longer cycle. Why don't replace deepCopy by veryDeepCopy, same behavior but copy each object only once (create collection and keep reference). performance issue ? _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
