FWIW Parts of the Carbon umbrella framework are 64-bit and may well remain even beyond macOS 10.15. However, some of the frameworks under the Carbon umbrella are still 32-bit and these will in all likelihood go away someday (maybe even with macOS 10.14). To my knowledge Apple stated that macOS High Sierra would be the “last macOS release to support 32-bit apps without compromise” (whatever that might entail) and implied that macOS 10.14 would begin “aggressively” warning (again subject to interpretation) users about 32-bit apps.
Of course if one goes digging one can see that a number of Carbon APIs have been converted to 64-bit that Apple does not officially make public. When I asked about this some years back Developer Technical Support indicated that making the APIs public would require extensive corporate resources and as the direction of the company was to move away from Carbon especially HIToolbox and similar technologies they were never going to be publicly available. However, just because an API is not publicly available does not mean that Apple does not use it in their own applications. As an example using nm on HIToolbox shows 23,539 symbols for 32-bit but only 19,672 for 64-bit on macOS 10.12 and an example of an API that is not available in 64-bit there is no _FindControl in 64-bit. The 19,672 could, however, remain available even after macOS 10.15 with what ever ones that are publicly available remaining public available and whatever APIs that are not publicly available remaining privately available to Apple. WRT iTunes my guess would be that some portion of the application is still dependent on technologies currently included in the Carbon umbrella framework. It should not be too difficult to obtain a list of the symbols from the Carbon framework that iTunes uses if one really wanted to know what it uses. For myself I found that porting to Cocoa was much easier if I simply abandoned many of the Carbon ways of doing things and used technologies like bindings, operation queues, blocks (closures) and otherwise let AppKit do much of the work for me. Moving from the Carbon Print Manager to Cocoa printing was trivial once the rest of the application was using AppKit and it was almost not work to move printing off the main thread to avoid holding up the rest of the application. —kevin > On Jun 27, 2017, at 3:00 PM, carbon-dev-requ...@lists.apple.com wrote: > From: Igor Delovski <idelov...@gmail.com> > Subject: Re: Is Carbon dead? > Date: June 27, 2017 at 9:21:02 AM EDT > To: "Ann K. Blombach" <a...@macgamut.com> > Cc: Brendan Shanks <bren...@bslabs.net>, Carbon-Dev > <carbon-dev@lists.apple.com> > > > Before the list goes away, I'd like to add few points. > > I have one app depending on carbon. Carbon is dead for a long time but the > framework is still present in all modern Mac OS versions. With the help of > lsof cammand line utility I can see that iTunes is using Carbon framework. > All apps made with Qt seem to depend on Carbon.framework. Yet, iTunes is a 64 > bit application. It would be nice if someone knows how they managed to do > that. Plugins? Dylibs depending on carbon? > > And another thing. > > At some point 15 years ago I moved my carbon app to Windows by designing a > Win32 layer that emulated certain parts of carbon and it enabled me to reuse > my DITL resources to recreate all the dialogs and wondows on Windows. Now I'm > almost sure I'll do it again with cocoa. It will probably take some time but > it would let me to move that app not only to 64bit Mac but eventualy to iPad. > > Maybe there is someone with similar projects on this list? Anyone would like > to collaborate on this? Any examples of modal loops? If I could see the code > behind the WaitNextEvent in CoreFoundation or NSEvent it would help me > properly handle modal loops I use with modal dialogs or longer processes like > printing. > > Igor > > > On Wed, Jun 7, 2017 at 10:50 PM, Ann K. Blombach <a...@macgamut.com > <mailto:a...@macgamut.com>> wrote: > Thanks to the folks who replied. It was easier to ask the list than to keep > searching for the answer. I’m obviously not at WWDC. That’s about when I > will likely retire anyway (I’m 71, so it may be time), so this is great news. > I know Apple has warned us for years that Carbon was “deprecated,” but I’m > too old to start over once again! But this gives me enough time to either > find someone else to carry on my work or else warn my loyal users about > what’s coming. > > > > Again, thanks, >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (Carbon-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
