> (one) place. You're doing something wrong if you're creating external > code files that are designed to have many places update with the same > actual textual code, which you are aiming at changing in one location > and having multiple places in the external files update textually and > redundantly from that. Code isn't like that: you call a function that > resides in its one right place, and update that single instance of > that function, not replicate the text of that function all over.
The first time I ran into clone problems was when I duplicated a batch file to two different file system locations. The first is within my Code tree, which is under revision control, and thus vital. The second is in a shared Bin directory in PATH, the place where the script is actually *used*, and thus also vital. If it were only one computer I could make z:\bin\foo.bat a simple `@call c:\code\foo\foo.bat %*` and thereby sidestep the duplication issue. I needed to make the .bat available to more than one computer and b:\code is only there for me. So now I have a third script, publish-foo.bat, which copies from code to bin. This works and is safe, but has friction compared to the stupendous aha's "edit, alt-f4, edit, alt-f4..." I was looking for. So it's wrong in that DRY is violated, but I really don't see any other way of doing it. (I'm not offering this as a complaint, just an experience to contribute to the context.) -- -matt -- 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.
