Apple has historically suggested using ICU for functionality that it's
higher-level frameworks don't provide, and it's easy enough to get at all
needed functionality through its C functions without using C++ (at least what I
care about). Since most significant changes only occur in the data
On 6 Oct 2016, at 10:43, dangerwillrobinsondan...@gmail.com wrote:
>
> Pretty sure the reason is a simple one.
> If you look at the history of open source in the OS on the Apple open source
> page, you'll notice they pretty much bump the ICU version they use annually.
> Although unlikely, ICU
Pretty sure the reason is a simple one.
If you look at the history of open source in the OS on the Apple open source
page, you'll notice they pretty much bump the ICU version they use annually.
Although unlikely, ICU might change in ways that breaks your app. They don't
want to support ICU
My experience has been that last year (iOS 9 and OS X 10.11) Apple made ICU a
private framework worthy of rejection from its App Store if you used its APIs
directly. I encountered this because like in years past when Apple did not
provide ICU through a higher-level framework, we were encouraged
The Icu stuff (57.1) is included in macOS 12.
There is:
/usr/lib/libicucore.A.dylib
and Xcode has:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libicucore.tbd
But I cannot find the headers.
Gerriet.
