Bill wrote: > Unwieldy in my mind means I *have* to do a lot of complicated things > in order use the tool effectively. The mere existence of complex > functionality simply means the tool is powerful.
I was meaning unwieldy from a maintenance point of view. For example, Programmer A writes a bunch of complex NAnt build files using lots of procedural features and string manipulation. Programmer A leaves the project. Programmer B is assigned to the project and has to become a NAnt expert to fully understand/maintain the build process. > Forcing the user to use the script task (or a custom task) to accomplish > something (Gerry's example), when a cleaner solution could be had (even > if that feature has other powerful uses) could actually make the tool > unwieldy. I agree with this. But the example provided does not in itself justify the function library and procedural features we are talking about. > > Best, > Bill > > William E. Caputo > ThoughtWorks, Inc. Mark ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
