Hello Ian, >>If anything, I would think that the xpath expression language would be a >>good start. I'm not sure if I would want an expression language included >>with nant though. This could however be an addin, or extension. Adding >>expressions (as we have discussed before) seems to me to be just one more >>complicating feature for NAnt. >> IM> Actually condition support would be considerably simpler ( from a users IM> point of view ) than a plethora of nested condition tags. AFAIK, it is relatively easy to implement xpath expression language using the System.Xml.XPath.XPathNavigator and System.Xml.XPath.XPathExpression classes, moreover it is possible to implement custom xpath functions by deriving from XsltContext and calling SetContext method with an instance of that derived class on XPathExpression we are executing.
I can try to implement all the things I've written above but I'm not sure if I have the same vision of this feature, it would be great if someone explain his vision of the whole thing. -- Best regards, Ivan mailto:[EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
