>From: "Gert Driesen" <[EMAIL PROTECTED]> >Sent: Monday, August 02, 2004 4:28 PM
> The release notes for the NAnt 0.85 beta 1 are ready for review here : > http://nant.sourceforge.net/releasenotes.html (and in cvs ofcourse). With respect to the latest item: Automatic quoting of arguments (built-in type) has been removed for non-file arguments (<arg value="...">). This breaks build files that assume that argument values containing spaces will be quoted. I was confused when this was first announced in the last few days, but didn't have time to comment then. If the reader isn't particularly familiar with the <exec> task, then the <arg> type may be unfamiliar as well. My initial reading was that this was talking about arguments to built-in functions, and the example was simply poor. It also assumes that the reader was aware that automatic quoting was taking place, a point that's not mentioned in the <arg> documentation. Finally, there's confusion as to when the quoting is taking place - as part of the parsing of the build file (which really confused me, as I always thought XML required quotes on all attribute values) or when passed to the <exec> task - especially before I realized that <arg> was used by <exec>. For this item, I suggest: Previously, the <arg> type (used by the <exec> task) would automatically add quotes to both "file=" and "value= attributes", so that they'd be quoted in the command line generated by the task. That automatic quoting has been removed for "value=" attributes (but not for "file=" attributes), because .... In general, with release notes about behavior changes, I always found that general style (Previously ... Now....), although wordy, saves me the trouble of having to look up things in the manual just to understand the release note and figure out whether or not I cared. Gary PS: Part of the problem is just the terminology. NAnt uses "type" in two ways, one for the types of items within expressions, and one to certain constructs that can be used as task elements. I've never been fond of the latter use, mostly because it's not introduced well in the documentation, but also because extrapolating the use of the word "type" from conventional programming languages to NAnt syntax is unfamiliar and feels unnatural ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
