The bug is currently wrong. unicode::code_point is defined to be
uint32_t when ZORBA_NO_ICU=ON.
** Summary changed:
- ZORBA_NO_UNICODE and fn:codepoints-to-string()
+ ZORBA_NO_ICU and fn:codepoints-to-string()
** Changed in: zorba
Status: New => Invalid
--
You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.
https://bugs.launchpad.net/bugs/867124
Title:
ZORBA_NO_ICU and fn:codepoints-to-string()
Status in Zorba - The XQuery Processor:
Invalid
Bug description:
When Zorba is compiled with ZORBA_NO_ICU=ON, the function fn
:codepoints-to-string() defined in strings_impl.cpp won't compile
because it makes reference to utf8::encode() that takes a
unicode::code_point argument. When ZORBA_NO_ICU=ON, the unicode
namespace is not declared, so of course code_point is not declared.
The solution suggested on zorba-coders was to disable (not compile) fn
:codepoints-to-string() -- and probably any other XQuery function that
involves code-points.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/867124/+subscriptions
--
Mailing list: https://launchpad.net/~zorba-coders
Post to : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help : https://help.launchpad.net/ListHelp
