Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am dealing with some auto-generated XSLT code.
It contains the following:
string(string(.))
number(string(.))
string(number(string(.)))
Is there any point to these? Or are they reducible to
string(.)
number(.)
string(.)
?
Like Martin says.
There are edge cases in XPath 2.0 where number(string(.)) is not exactly the same as number(.), for example if the context item is an instance of xs:gYear then number(.) will fail but number(string(.)) will succeed; contrariwise, if the context item is a boolean, number(.) will convert true to 1 and false to 0, while number(string(.)) converts both to NaN. But it’s very unlikely that these edge cases are important to your application.