I have a series of little @file programs, all in the same outline, that use a skeleton that is nearly the same. For each new one, I copy the skeleton and then modify it. One or more of the nodes, however, are always the same. I clone that node, so that if I make an changes or fixes, all the programs get the changes to that node.
What should happen when I copy a tree that contains a clone? I assumed that the new tree would contain yet another clone of that node. But what I actually get is a copy of the original node, not a clone. I deal with this by cloning the desired node, then deleting the unwanted copy. What is the intended behavior when a tree containing a cloned node is copied? Should the clone be turned into a copy of its parent node, or another clone. Personally, I think it should be another clone. (Just for a little context, these programs are intended to be used as Unixy filters that act on X-Y data that is contained in two-column text files that may contain comments or meta data. A typical use might be like this: type datafile | timeshift -s 5 | scale -s 11.5 | diff | smooth -w 10 | plot (This is for Windows - for Linux, of course, you would cat datafile instead). Since they all read the same kind of data from stdin, write the same data format to stdout, read similar command line options, etc, the skeletons are nearly but not exactly the same. However, the code that turns the text data into numbers is always the same - it has to be or the pipeline components wouldn't work together. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/7fbd352e-12e1-4bca-a01e-7a04a429d514%40googlegroups.com.
