res files) can be copied to that location to provide new locale data or conversion tables etc. If a path is set, then single data files (e.g. dat package file makes the opposite trade-off: Platform-portable (except for endianness and charset family, which can be changed with the icupkg tool) and modifiable (also with the icupkg tool). This is convenient because it requires no install-time or runtime configuration, but the library is platform-specific and cannot be modified. dat file: By default, the ICU data is built into a shared library (DLL). Note: The ICU test suites can be compiled with this setting. Use of any of these macros should be replaced as noted in the comments for the obsolete macro. Beginning with ICU 60, you should define U_HIDE_OBSOLETE_UTF_OLD_H to 1 (via -D or uconfig.h, as above). ![]() utf_old.h: All of utf_old.h is deprecated or obsolete.Note: The ICU test suites cannot be compiled with this setting. Beginning with ICU 49, you should define U_NO_DEFAULT_INCLUDE_UTF_HEADERS to 1 (via -D or uconfig.h, as above) and include those header files explicitly that you actually need. All of utf_old.h is deprecated or obsolete. Often, none of them are needed, or only one or two of them. ![]() utf.h, utf8.h, utf16.h, utf_old.h: By default, utypes.h (and thus almost every public ICU header) includes all of these header files.Note: The ICU test suites cannot be compiled with these settings. Consider marking the from- const char* and from- const UChar* constructors explicit via -DUNISTR_FROM_STRING_EXPLICIT=explicit or similar.Consider marking the from- UChar and from- UChar32 constructors explicit via -DUNISTR_FROM_CHAR_EXPLICIT=explicit or similar.Beginning with ICU 49, you should do the following: This can lead to inadvertent construction of a UnicodeString with a single character by using an integer, and it can lead to inadvertent dependency on the conversion framework by using a C string literal. UnicodeString constructors: The UnicodeString class has several single-argument constructors that are not marked “explicit” for historical reasons.+++ source/common/unicode/utypes.h (working -160,7 +160,7 UCONFIG_NO_CONVERSION source/common/unicode/utypes.h (revision 26606) You could temporarily (until you have more time to update your code) revert to the default “using” via -DU_USING_ICU_NAMESPACE=1 or by modifying unicode/uversion.h: If your code relies on the “using namespace icu ” that used to be in unicode/uversion.h, then you need to update your code. Namespace (ICU 61 and later): Since ICU 61, call sites need to qualify ICU types explicitly, for example icu::UnicodeString, or do using icu::UnicodeString where appropriate.Note that C99 compatibility is now required. How To Build And Install On The IBM i Family (IBM i, i5/OS OS/400)ĭepending on the platform and the type of installation, we recommend a small number of modifications and build options. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |