on 2011 Nov 22 5:49 PM
Problem compiling app for iOS when changing from 12.0.0 to 12.0.1 - Unicode API no longer available
The UltraLite headers that are included in an iOS application have changed from 12.0.0 to 12.0.1. My application uses APIs and types that are defined under this condition: #ifdef UL_WCHAR_API . However, upgrading the version, and without changing anything else, UL_WCHAR_API is no longer defined, and the API and type definitions are no longer accessible. Trying to force the definition creates other problems such as ambiguous definitions, etc. Has anyone else had this problem? Is there anything we can do to safely enable this define?
Running on MacOSX Snow Leopard 10.6.7, XCode 4.2, iOS SDK 5.0
Thanks in advance.
The WCHAR (2-byte UCS-2/UTF-16) API is only supported on Windows platforms (where wchar_t is 2 bytes). The intention is that UTF-8 is used on iPhone.
Having said that - can you explain why you are using the wide APIs?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have now added UTF-16 APIs on iOS for streaming character data to and from the database - available in the next EBF (12.0.1.3713 or later). The APIs are:
ULPreparedStatement::AppendParameterStringChunk ULResultSet::GetStringChunk ULResultSet::AppendStringChunk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
75 | |
10 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.