On Tue, 15 Apr 2008 13:01:49 -0500
"Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> > I would have thought, if unified nodes have both a children list
> > and a parent list, which I think they do according to a previous
> > email, a node n is cloned iff len(n.parents) > 1?
>
> That was my first thought too. But two clones can share the same
> parent.
Yes... but they must also each have at least one additional parent in
order to be clones? So len(n.parents) > 1 holds?
I've been becoming increasingly unsure about the definition of "clone"
in the unified node world. At least, I see no problem mapping
current Leo's "clones" to the unified node world, but the discussion
using the term clone, I'm not sure we're on the same page.
Data:
A-+
|
+-B
|
+-C-+
| |
| +-F
|
+-D-+
|
+-E
|
+-(to C)
Alternative view, same data (this is a DAG, just assume
arrowheads as needed):
A-+
|
+-B
|
+--------------+
| |
| |
| |
+-D-+ +-C-+
| | |
+-E | +-F
| |
+----------+
Leo tree widget presentation:
A-+
|
+-B
|
+-C*-+
| |
| +-F
|
+-D-+
|
+-E
|
+-C*-+
|
+-F
Narrative:
Node C is "cloned". There is only one C node. "*" is the Leo clone
indicator. Node C occurs in the children lists of both A and D. Node
C has two entries in its parents list, i.e. A and D. There is only
one node F, and it has only node C on its parent list. In the
vnode/tnode world you'd say the Fs are joined (I think?), but they're
the same node, so this is redundant.
Cheers -Terry
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
