On Jul 4, 2:00 pm, "Edward K. Ream" <[email protected]> wrote:
> In the new world, Leo would never copy nodes. Instead, it would > simply create another pointer to the cloned node in the parent's > children array. Thus, the same node could appear in several places in > the same child list. BTW, this would also be the end of tnodes, and all the confusion regarding vnodes vs tnodes, t.uA's vs. v.uA's, etc. etc. For compatibility with old scripts, v.t == v for all nodes v, but eventually all references to v.t will disappear. Ditto for many other tnode-related concepts, such as tnode-related iterators. By default, Leo's file format will remain unchanged. However, Leo 4.7 also aims at allowing various new formats for .leo files, so we have an interesting design playground to explore. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
