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 across releases, or below an API layer, the interfaces would not be as much of an issue for most when using the current installed library. -- Gary L. Wade (Sent from my iPad) http://www.garywade.com/
> On Oct 6, 2016, at 5:23 AM, Alastair Houghton <alast...@alastairs-place.net> > wrote: > >> 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 might change in ways that breaks your app. They don't >> want to support ICU directly. It's a pretty tough API in C or C++ > > Also, historically, C++ ABI compatibility has been a thorny issue. Even now, > if you want a C++ dynamic library to provide binary compatibility you have to > be pretty careful. > > ICU is largely a C++ library. It does have a C interface, but I’m not sure > the entire feature set is available without using C++, and ICU explicitly > doesn’t provide for binary compatibility at the C++ API level (or even for > some of its C API(!)) - see > > http://userguide.icu-project.org/design#TOC-ICU-Binary-Compatibility:-Using-ICU-as-an-Operating-System-Level-Library > > Kind regards, > > Alastair. > > -- > http://alastairs-place.net > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
