Hello,
you got it. It is only difference.
Reasoning:
There are scenarios where you have to test, whether some element/attribute
is present in the xml. Its _not_ an error, if such element/attribute is
missing. Since xmlpeek task report it via exception, and even with
failonerror set it is
Hi, MartinOn 30/01/06, Martin Aliger [EMAIL PROTECTED] wrote:
Hello,I like it very much. Expecially functions. Bad luck I personally neednamespace support, since mine xmls have some namespace in it. And evendefault namespace needs specification in xpaths :-(
I don't know that much about
Martin,
Overloading of functions is not (yet) supported. I'm definitely in favor of
this, but if I recall correctly Ian and Jarek ruled against this in favor of
implicit conversion of function arguments. Ian, please correct me if I'm
wrong.
Gert
- Original Message -
From: Martin Aliger
Hi, Martin,I've knocked together the following two functions. I haven't tested them yet, but they don't exactly work ideally anyway. I want to be able to have a params array of XmlNamespace[] as the last parameter, but it won't let me do that because, apparently, XmlNamespace needs to implement
Actually, scratch that. It seems that it needs to implement IConvertible if it needs to pass to that function. I'll carry on looking at it, and let you know how I get on.On 30/01/06,
John Ludlow [EMAIL PROTECTED] wrote:
Hi, Martin,I've knocked together the following two functions. I haven't
Martin Aliger wrote:
Reasoning:
There are scenarios where you have to test, whether some element/attribute
is present in the xml. Its _not_ an error, if such element/attribute is
missing. Since xmlpeek task report it via exception, and even with
failonerror set it is considered error, blaming
