[self-interest] deep copy
janpaulbultmann at me.com
Sun Dec 26 23:40:40 UTC 2010
No, I think David is refering to problems that arise for example when deep copying morphs.
The clone on a morph will go in two steps, first make a copy tree (a deep copy if you will). But then start to reconect this tree, so that you get everything as wanted.
Let me do an Example:
What if you copy an outliner morph. Do you want all the buttons too? Of course. But do you wan't a copy of the object the outliner looks at? No. Do you wan't the debugger process to be cloned, so you can play with it in a different way, or do you want the old one? No idea :D this is where it gets sticky.
On Dec 27, 2010, at 12:35 AM, Casey Ransberger wrote:
> Why's that? Messiness with cycles?
> On Dec 26, 2010, at 3:18 PM, ungar at mac.com wrote:
>> Deep copy is a fallacy.
>> On Dec 26, 2010, at 3:16 PM, Jan-Paul Bultmann wrote:
>>> no deep copy functionality there?
>>> cheers Jan
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Self-interest