I admit I have never fully understood the concern, but Lewis' Art and Science makes reference to flaws in #deepCopy. Not much to go on, but pg. 60 in my copy. It is a good book, so I do not easily dismiss what he says. At around the time I saw that, #postCopy came to my attention - connection???
Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lukas Renggli Sent: Wednesday, January 13, 2010 2:54 AM To: [email protected] Subject: Re: [Pharo-project] clone vs shallowCopy > #clone and #shallowCopy have a difference in their semantics. If the > vm cannot allocate enough space for the new object, #clone raises an > error immediately, while #shallowCopy signals the low space semaphore, > so the image or the user can do something, then retries the copying. Do we really need that? It would be cool to merge #clone and #shallowCopy, and all the different #deepCopy* instances. Also the implementation of #deepCopy might need some cleanup, it seems to be rather complicated for such a trivial task of copying a object graph. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ 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
