> #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
