On Aug 30, 6:27 am, "Edward K. Ream" <[email protected]> wrote: > Rev 2356 of the trunk contains what I hope will be the last major bug > fix related to caching and unified nodes.
I plan to enable g.unified_nodes in the trunk tomorrow. I have been eating my own dog food without any problems for several days. This transition must happen eventually, and I know of no reason not to do this sooner rather than later. If you object to this, please let me know. However, you can always set g.unified_nodes switch = False to use Leo's legacy data structures. Transition plans - I must revise the scripting chapter extensively to discuss unified nodes. This is good: the unified nodes world is much simpler conceptually. - Work on clean-one-node branch is complete, but I won't merge that branch into the trunk until after I return from vacation at the end of September. This will allow people to avoid the new code by setting g.unified_nodes = False. - The one-node branch simplifies the code on the assumption that g.unified_nodes is True. However, several other simplifications are possible throughout Leo's core. For example, we can simplify or eliminate iterators, and we can convert t or v.t to v. These kinds of simplifications will happen later, in a new branch called something like clean-one-node2. 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 -~----------~----~----~----~------~----~------~--~---
