On Wednesday, June 13, 2018 at 8:08:38 AM UTC-5, Edward K. Ream wrote: Handling nested clones properly while scanning the text of the external > file is more tricky than I imagined. >
Rev e1bd6c0f2 in the fast-read branch passes all my present tests. It replaces in in_clone_tree boolean with clone_v, the root of each clone tree. So now clone_v gets pushed on the level stack instead of just a boolean. In retrospect, maintaining a tree of clones is essential. The new code contains a strange hack that seems to work. When creating a new clone_v, we clear its children. Within the scanned descendants, only the immediate children add themselves to clone_v.children. More testing is needed. The new code tries to ensure that data from the .leo file doesn't bleed into the @file trees. I haven't tested this yet. That's coming soon. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
