I haven't looked into sentinels and @shadow, I only know that they are there and that @shadow is a means to reconstruct a Leo file when sentinels are absent in an external file. So the following might be completely irrelevant to the topic. That said, I get the impression that you are mixing two problems:
1. Leonard and Linda exchanging data and structures via (Leo generated!) files. Both are Leo users. So you can rely on the tools Leo offers; and it's reasonable to assume that one can consolidate both their file versions. 2. Nancy comes into play. Once files are out in the wild, you have absolutely no control over what will happen to them. No matter how good the @shadow is, one can always imagine just one more change that will break the best @shadow algorithm. Basically for me this boils down to: I want to throw an arbitrary file at my @shadow (or whatever better solution will be developed), and it shall be able to reconstruct the original structure, even if the structure in the file is upside, all the names have been changed, the file has grown or shrunk by a factor of two (whatever), or even it doesn't have (or had) any discernible at all. Is this doable? -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
