somthing like this could be a good solution. Another possibility is to
have a way to set an attributes value such that its equivalent to it not
being set - somthing like null for attributes. For example;
<target name="notdoc">
<property name="docFile" value="${property::null-value()}"
</target>
<csc target="exe" output="..." doc="${docFile}/>
Ian
That certainly looks simpler to implement, and it seems equally powerful in terms of optional attributes. I think I'm leaning towards this as a better solution... because it doesn't introduce any new structures the learning curve should be lower; it also doesn't require any arbitrary rules like "cannot dynamically set if/unless". Possibly the only issue that I can think of is a nit-pick... where would you document the null-attribute behaviour so people can find it?
I guess the _expression_ help page for new users, and the release notes for old users? I just wonder if the _expression_ page isn't the obvious place to look for attribute behaviour.
--
Troy
