On Jul 10, 2015, at 5:31 PM, Ben Kennedy wrote:
>> Once Yosemite stops being updated, we can of course use the constant for the
>> last version that’s released, but since we still can’t say with 100%
>> certainty that there won’t be a 10.10.5, we can’t really rely on this.
>
> No kidding. (Nev
On Jul 10, 2015, at 7:31 PM, Ben Kennedy wrote:
>
> On 10 Jul 2015, at 12:01 pm, Charles Srstka wrote:
>
>> What this means is that if you try to use an El Capitan-only feature and put
>> it in a block that starts with a check on floor(NSFoundationVersionNumber)
>> or floor(NSAppKitVersionNum
On 10 Jul 2015, at 12:01 pm, Charles Srstka wrote:
> What this means is that if you try to use an El Capitan-only feature and put
> it in a block that starts with a check on floor(NSFoundationVersionNumber) or
> floor(NSAppKitVersionNumber) to make sure it’s larger than the value for
> 10.10.0
Just thought I’d like to warn everyone about something:
In the past, the NSFoundationVersionNumber constants for the same major OS
version always used to have the same integer component. For example, the
constants for 10.8, 10.8.1, 10.8.2, 10.8.3, and 10.8.4 are 945.00, 945.00,
945.11, 945.16,
