[CocoaApp isThisTiger]

Christiaan Hofman cmhofman at gmail.com
Tue Oct 23 04:54:41 PDT 2007


On 23 Oct 2007, at 1:35 PM, Finlay Dobbie wrote:

> On 23/10/2007, Finlay Dobbie <finlay.dobbie at gmail.com> wrote:
>> On 23/10/2007, Christiaan Hofman <cmhofman at gmail.com> wrote:
>>> That should be in the main System version of NSApplication.h on
>>> Leopard. Certainly not in the 10.4u SDK, because that SDK is
>>> available on Tiger, and Tiger doesn't (officially) know it's last
>>> AppKit version number yet.
>>
>> NSAppKitVersionNumber10_4 would correspond to the AppKit version
>> number of 10.4.0, surely?
>

Sorry, you're right. But though this might not be the reason then, it  
*is* a fact that NSAppKitVersionNumber10_4 is not defined on Tiger,  
but only in Leopard (and later) Just as NSAppKitVersionNumber10_3 was  
only defined on Tiger. I guess the idea is that an app developed on  
Tiger should not try to use Leopard features, so why should it care  
to check for Leopard?

Christiaan

> And just for completeness, that is 824.
>
> #ifndef NSAppKitVersionNumber10_4
> #define NSAppKitVersionNumber10_4 824
> #endif
>
> When Leopard comes out, if NSAppKitVersionNumber10_5 is not defined,
> you will obviously be able to use the same trick (just write a one
> line tool to print out the actual value of NSAppKitVersionNumber in
> the GM).
>
>  -- Finlay



More information about the MacOSX-dev mailing list