When two clones have the same parent (e.g., immediately after the
clone node operation) wouldn't they list the same parent twice in the
parent list?
- Stephen
On Apr 16, 9:19 am, derwisch <[EMAIL PROTECTED]>
wrote:
> On Apr 15, 8:01 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
>
> > That was my first thought too. But two clones can share the same parent.
>
> Ouch. That's where the DAG analogue breaks, or even the analogue with
> graphs in general. Didn't think of that.
>
> In order to maintain the analogy, would it be possible to disallow
> "identical twins", so to say? Obviously this would mean getting rid of
> the Clone Node function and having "Paste node as clone" as the normal
> way of producing clones. Or are there use cases for having multiple
> clones as siblings?
>
> On a related note, how would unified-node versions of Leo handle
> legacy files? Will there be an import function? If you'd be willing to
> make a change taht radical, the import function would then merge
> idenical twins to a single node (and give a warning about it).
>
> I am boldly proposing this for three reasons: Out of some kindergarten
> spite ("you destroy my card house, so I'm destroying someone else's"),
> because I am right now seeing no use for identical twins, and because
> I think it is a very good idea to keep the analogy to some very well
> described and explored mathematical structure.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" 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
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
