NSAppKitVersionNumber10_5[_1]

[Christiaan Hofman]

I'd say it should be 949. Note that not all minor versions get their  
own AppKit version number, probably because AppKit remains unaltered  
(e.g. NSApplication.h declares only 4 different version numbers for  
10.3). Looking at existing version numbers there is a consistent  
pattern: AppKit version numbers of the same major OS release have the  
same integral part. Moreover the one without a minor version part  
(like NSAppKitVersionNumber10_4) is always equal to this integral  
part. If you think about it, this is an important requirement,  
otherwise the standard checks like 'if (floor(NSAppKitVersionNumber)  
 > NSAppKitVersionNumber10_4)' could never work.

Christiaan

On 30 Jan 2008, at 7:13 PM, Martin-Gilles Lavoie wrote:

> Greetings
>
> It's been already discussed/reported that Mac OS X SDKs dont define  
> their current target OS release version.
>
> Eg: in Leopard, NSAppKitVersionNumber10_4 is defined and so are  
> most previous(/meaningful) ones but the 10.5 SDK does not define
>
> 	NSAppKitVersionNumber10_5
> nor	NSAppKitVersionNumber10_5_1
>
> For the curious, 10.5.1 is valued at 949:
>
> #ifndef NSAppKitVersionNumber10_5_1
> #define NSAppKitVersionNumber10_5_1   949
> #endif
>
> It's yours to keep. Have fun.
>
> But, does anyone have 10.5 version handy?
>
> It feels silly for me to re-install the OS just for that. You can  
> check at runtime the AppKit version using the extern symbol
>
> 	NSAppKitVersionNumber
>
> and looking the value from the debugger of NSLog-ing/printf-ing it.
>
> Thanks for sharing.
>
> Martin-Gilles Lavoie | Senior software developer | 514.905.8658
> Oracle - Macintosh Native Desktop Client, Beehive
> 600, boul. de Maisonneuve West, Suite 1900 | Montréal (Québec)  H3A  
> 3J2
>
>
> _______________________________________________
> MacOSX-dev mailing list
> MacOSX-dev at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/macosx-dev