On Wed, Jan 18, 2012 at 5:00 PM, Seth Johnson <[email protected]> wrote: > > But my point is that the concept of templating is fundamentally at > odds with maintaining a codebase. Therefore, if I'm getting what you > mean by cross-file clones, cross-file clones shouldn't automatically > do templating. > > So while people may have gotten excited with the prospects of doing > cloning even across external files, there's a difference in function > that seems to have been implemented without recognizing it.
You can group clones without regard for what external files they're in, willy-nilly, so long as what you're doing is creating views into a codebase, wherein files are maintained independently, and never making one a clone within another (which is a different purpose). True? Then: make templating something different from clones under @file. Indeed, it strikes me you don't want any clones under @file. But you could implement, and handle distinctly, something like an @template thingie, where you can paste any clones you please, and the purpose of that is to make an external file built out of those pieces, which can dynamically change. Plus, you can have a way of specifying the order of priority processing issues (presently called "clone wars"), maybe a variety of selectable algorithms, associated with @template branches. Stabbing in the dark a bit here, because I am not sure I get the cross-file clone thing, but if I'm right, aren't my inferences correct? Seth -- 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.
