On Fri, Mar 26, 2010 at 11:50 AM, Chas Emerick <[email protected]> wrote: > Because they're common processes that are ideally built once, and then > reused with minor variation. Library reuse is generally considered to be a > good thing in software development, so it strikes me as odd that many think > that such practices should stop at the build's edge, as it were.
Reuse is great. Integration tends to hamper reuse. To take one of your examples, if I want to bundle my classes and dependencies into a Windows installer, I will call a function in a library (or a command line program in the Unix world) that does that. That's it. It doesn't need to be part of the build system and shouldn't be. I can call functions in the build system to supply the relevant arguments. If the build tool and library is well designed, the added value of integration in this example should be infinitesimal. -Per -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en To unsubscribe from this group, send email to clojure+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
