Norman,
good to know. At least I'm not doing something wrong.
Thanks,
Tomas
On Nov 17, 2006, at 9:08 AM, Tomas Camin wrote:
Hi,
I'm parsing a xml file. Some of the fields I'm looking for doesn't
always exist in the xml file so I'm doing the following:
dim n as XmlNodeList
try
n=node.Xql(value)
Catch
return ""
end try
If the field "value" is missing then I get a XMLException and a
XMLDomException so I putted a single catch, instead of doing 2
separated catch err as XMLException and catch err as XMLDOMException.
Is there a better way to do a xql query with missing fields?
While debugging the app it's quite annoying to have to turn off
"break on exceptions" as these exceptions are *expected* while
others might not be expected and it would be useful if the
debugger could catch them.
There's been a very long explanation of why this is darned hard, if
not impossible to do.
The catch could be anywhere up the call stack, and that could vary
at run time.
So, do it this way and just live the the fact that when you debug
either turn break on exceptions off or that you will break into the
debugger BUT can continue
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
