>From: "Jamie Briant" <[EMAIL PROTECTED]> >Sent: Wednesday, January 26, 2005 12:49 AM
> The first is dangerous because when a programmer decides to change some > build.config's to build.local.config (for example) they are guaranteed > at some point to miss one. Not every time. Not even very often. Just > often enough for the failure to be costly. I'm not sure how this could happen with an automated replace and a proper review, and I hope that no one would make this sort of edit manually. But you could just as easily have typos elsewhere that are just as fatal; as I said recently, the <read-my-mind> task still isn't implemented. >If the word "overwrite" is confusing, may I suggest a new option be put > in its place that has the same effect, such as "overwriteexisting", or > "lookmeupinthemanual". If you're going to do that, you may as well make it "ICouldNotForTheLifeOfMeFigureOutAWayToMakeThisUsableSoIPutInThisUnusa bleNameInstead" :-) A while back, I suggested that the "default" pattern occurs often enough to be put into the property mechanism. Something like either <property name="build.config" default="default.value"/> , which would have the same effect as the other two, or even something like <default name="build.config" value="default.value" /> , again with the same effect. This is the wrong time to put this back on the table, but it's certainly reasonable enough to consider in the future. Gary ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
