I actually have to agree with Clayton in some way ...Why ? The ability to have conditions I can see but you state that that is another advantage. Sure a more verbose description can be more explicit but remember that people have to type this stuff into an editor and adding 2 levels of nesting for no appreciable gain in the the pursuit of explicitness is a hard sell. Imagine adding the same 2 levels of nesting to various c# control structures - there would be a public outcry and rightly so. Xml tends to be verbose enough as it is without us making it worse. In fact one of the commonly used arguments against using tools like Ant and NAnt is the verbosity of their file formats.
Verbose is not always bad, I would prefer this :
<csc>
<commandoptions>
<option name="foo" value="true"/>
<option name="bar1" value="true"/>
<option name="bar2" value="true"/>
<option name="bar3" value="true"/>
<option name="bar4" value="true"/>
<option name="bar5" value="true"/>
<option name="bar6" value="true"/>
<option name="bar7" value="true"/>
<option name="bar8" value="true"/>
</commandoptions>
</csc>
over this
<csc foo="true" bar1="true" bar2="true" bar3="true" bar4="true" bar5="true" bar6="true" bar7="true" bar8="true" />
any day ...
Of course there is always a trade off between terseness and expressiveness but I think in this case as in <csc> we can safely err on the side of less verbosity.
Ian
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
