Panther/Xcode and availability macros
Panther/Xcode and availability macros
- Subject: Panther/Xcode and availability macros
- From: Julien Dufour <email@hidden>
- Date: Mon, 3 Nov 2003 03:45:17 +0100
Hello
I have recently moved under Panther/Xcode, and I'm now getting troubles
using the availability macros, at least with the AppKit framework. It
seems that the MAC_OS_X_VERSION_MAX_ALLOWED setting has just become
unusable.
Mac OS X 10.3 has introduced new type definitions which are correctly
enclosed by some check like:
#if MAC_OS_X_VERSION_MAX_ALLOWED >= MAC_OS_X_VERSION_10_3
...
#endif
However, those new types are later used in other declarations which are
not embedded in any similar check. They are always defined and the
header can obviously not compile if MAC_OS_X_VERSION_MAX_ALLOWED is
lesser than MAC_OS_X_VERSION_10_3. There was no such problem with
Jaguar's headers and I haven't found any related information in the
release notes.
I have found twice occurrences of that issue when setting
MAC_OS_X_VERSION_MAX_ALLOWED to MAC_OS_X_VERSION_10_2, but many others
could be buried in the headers.
- In NSGraphics.h, the NSShowAnimationEffect function uses the
NSAnimationEffect enum for its first arguments.
- In NSLayoutManager.h, the NSLayoutManager interface adopts the
NSGlyphStorage protocol.
Am I missing something or should I fill a bug report?
Best regards.
Julien Dufour
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.