Yep, that is a great idea. I'm a little worried about providing a function library and expression language in NAnt. Maybe we could allow JScript.Net syntax or something. It becomes a pretty slippery slope though. I wouldn't want to distract from build management to start work on a custom expression language.
I would like to see the kind of separation that XPath and XSLT have. One uses the other, but they are their own beasts. XPath is not XSLT, and XSLT is not XPath. It sure would be nice if a pluggable .Net expression language existed :) > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Shaw, Gerry > Sent: Monday, July 22, 2002 5:17 PM > To: 'Nant-Developers (E-mail)' > Subject: RE: [nant-dev] IFTask PropertyMissing parameter? > > I'm hoping in the long run to add a number of functions to the if/unless > attributes so that we can write the following: > > <property name="debug" value="false" unless="property-exists('debug')"/> > > What do people think of that? I could easily imagine a number of other > useful functions that could be implemented. > > By placing the test in the if/unless attributes all the tasks get the > benefit. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
