> Oh - we already mention it before. Would be great! And also + operator in
> expressions could be overriden to fileset merge :) And functions with
> fileset argument could exists instead of string as refid to fileset etc
etc
> etc...
The overload is a bad idea. Currently it has problems with strings
(concatenation) vs anything else (addition) and adding another exception
would be even more confusing.
> Still we should be compatible with current id="" syntax so typedefs should
> define property of its type?
That would be consistent. We'd have a single build state
(PropertyDictionary) instead of PropertyDictionary for simple values +
DataTypeBaseDictionary for complex values.
> Sum: +1 for it!
>
> btw: maybe we will find some nicer syntax for merging here? e.g.
> <property type="fileset" name="id1" value="${id1+id2}"/>
I would propose:
<property name="id1" type="fileset" value="${fileset::union(fs1, fs2)}" />
<property name="id1" type="fileset" value="${fileset::intersection(fs1,
fs2)}" />
<property name="id1" type="fileset" value="${fileset::difference(fs1, fs2)}"
/>
Jarek
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
