Project

Profile

Help

Forums » Help »

normalize-unicode() doesn't report FOCH0003

Added by Anonymous almost 19 years ago

Legacy ID: #3489249 Legacy Poster: marcvc (marcvc)

Michael, a negative scenario, and have to admit, a detail in the details. normalize-unicode() doesn't seem to report FOCH0003 when the first argumnet is a ASCII-only string. Example: normalize-unicode("abc","invalid") Regards, Marc


Replies (2)

RE: normalize-unicode() doesn't report FOCH00 - Added by Anonymous almost 19 years ago

Legacy ID: #3489832 Legacy Poster: Michael Kay (mhkay)

This is legitimate according to the rules in XPath section 2.3.4: as soon as a processor can determine that the result of an expression X is either a value V or an error, it may return the value V without doing further work to look for an error. Section 3.1.5 Function Calls reinforces this: "The order of argument evaluation is implementation-dependent and a function need not evaluate an argument if the function can evaluate its body without evaluating that argument." If the first argument to normalize-unicode is an all-ASCII string, then the result doesn't depend on the second argument, so it's not required that the second argument should be evaluated. Michael Kay

RE: normalize-unicode() doesn't report FOCH00 - Added by Anonymous almost 19 years ago

Legacy ID: #3490469 Legacy Poster: marcvc (marcvc)

Thanks for the clarification. And of course, fully agree. Thanks, Marc

    (1-2/2)

    Please register to reply