I've just suffered another data reversion. It appears that .leo files are interfering with external files.
The good news is that when things are broken there isn't much of a penalty for bold action :-) In any case, trying to live without clones is already unbearable. Attempting to restrict their use would be cowardly and stupid. It's cowardly for two reasons: 1. The principle that external files should override .leo files is simple and good. 2. Although more difficult than the average 10-minute bug, this problem is still relatively simple. Alpha particles are not to blame :-) This means there is a specific sequence of actions that will illustrate the problem. My job is to find those actions, preferably in a small .leo file. I plan to create two files, small.leo and smallRef.leo as test vehicles to replicate these problems. It would be stupid for at least two other reasons: 1. It's hopeless to decree rules for using clones that few will remember and none will follow. 2.We want to *increase* the range of acceptable usage for clones, not decrease it. With these marching orders, I plan to use this opportunity to tackle the dreaded resurrected nodes problem. At present, with the benefit of having *forgotten* the details, it seems that it should be possible to completely eliminate resurrected nodes. The idea is to delete all children of @thin nodes before reading the corresponding external file. The code may already do that, but somehow that strategy isn't working. It may be that in some cases we are using the old @file logic instead. That would cause confusion. I'll be studying the details soon, and inserting warnings or dumps for unexpected situations. But to repeat, the main thing is to reliably replicate the problem. I'll do that, or perish in the attempt :-) 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.
