> On Jan 28, 2016, at 3:09 AM, chris <[email protected]> wrote: > > On Wed, 27 Jan 2016 17:21:06 -0800, Eric Schlegel wrote: >> In any case, writing a Carbon app against the 64-bit API is not >> supported, and we reserve the right to break it at any time. For >> practical purposes, “writing a Carbon app” can be understood as “ >> writing an app that uses WaitNextEvent or RunApplicationEventLoop or >> ReceiveNextEvent, and does _not_ use -[NSApplication run], to run its >> main event loop.” > > So now I am confused. Until now I used the header files as the ultimate > reference. In CarbonEventsCore.h for example ReceiveNextEvent is > labeled: > AVAILABLE_MAC_OS_X_VERSION_10_0_AND_LATER > and there is no __LP64__ condition or deprecation note in the comments > either. > (Xcode 7.2, OSX 10.11.3)
That’s true, you can call ReceiveNextEvent, but there’s not a lot else you can do due to significant missing API. For example, you can’t create a window. >> There are _some_ Carbon API that are officially supported for 64-bit >> use in Cocoa apps. For example, the API for registering for a >> symbolic hotkey has no Cocoa equivalent, so you’re still free to use >> that, and we’ll make sure it keeps working. > > What is the ultimate reference source for this, if it's not in the > headers? The headers are essentially the ultimate reference. We will maintain API that is visible for 64-bit use in the headers; otherwise, not. -eric _______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/carbon-dev/archive%40mail-archive.com This email sent to [email protected]
