-dev@lists.apple.com
Sent: Thursday, February 25, 2010 4:04:35
Subject: Re: Deprecated APIs
On Feb 24, 2010, at 11:36 AM, Steve Christensen wrote:
> On Feb 24, 2010, at 11:04 AM, Bill Bumgarner wrote:
>> On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
>>>> That code uses
On Feb 24, 2010, at 11:36 AM, Steve Christensen wrote:
> On Feb 24, 2010, at 11:04 AM, Bill Bumgarner wrote:
>> On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
That code uses blocks, though, which implies that it will be compiled
using a later version of Objective-C. Will that code
Le 24 févr. 2010 à 20:36, Steve Christensen a écrit :
> On Feb 24, 2010, at 11:04 AM, Bill Bumgarner wrote:
>
>> On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
>>
That code uses blocks, though, which implies that it will be compiled
using a later version of Objective-C. Will t
On Feb 24, 2010, at 11:04 AM, Bill Bumgarner wrote:
On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
That code uses blocks, though, which implies that it will be
compiled using a later version of Objective-C. Will that code
really run on older versions of OS X?
The compile-time condi
On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
>> That code uses blocks, though, which implies that it will be compiled using
>> a later version of Objective-C. Will that code really run on older versions
>> of OS X?
>
> The compile-time conditional assumes that you're building against
On Feb 23, 2010, at 3:26 PM, Charles Srstka wrote:
On Feb 23, 2010, at 2:25 PM, Steve Christensen wrote:
As others have already pointed out, it's your choice of whether or
not to support a deprecated API method. When I decide to use OS
version-specific API methods, I code as follows. The be
On Feb 23, 2010, at 2:25 PM, Steve Christensen wrote:
> As others have already pointed out, it's your choice of whether or not to
> support a deprecated API method. When I decide to use OS version-specific API
> methods, I code as follows. The benefit is that, when you decide to support a
> min
On Feb 23, 2010, at 2:09 AM, charisse napeÿf1as wrote:
I am not sure if this problem has already been submitted but how do
I define two APIs, one that is supported from Leopard down and
another that is only supported in Snow Leopard if I only have one
binary for all OSes?
Below is a sni
ruary 23, 2010 1:41 PM
Subject: Re: Deprecated APIs
> But is it still safe to use depracated APIs?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the
Am 23.02.2010 um 14:41 Uhr schrieb charisse napeÿf1as:
But is it still safe to use depracated APIs?
Did you read the document I pointed you to?
I quote:
"Note: Deprecation does not mean the immediate deletion of an
interface from a framework or library. It is simply a way to flag
in
I guess so. But is it still safe to use depracated APIs?
From: Andreas Mayer
To: cocoa-dev@lists.apple.com
Sent: Tuesday, February 23, 2010 20:29:47
Subject: Re: Deprecated APIs
Am 23.02.2010 um 11:09 Uhr schrieb charisse napeÿf1as:
> I am not sure
Am 23.02.2010 um 11:09 Uhr schrieb charisse napeÿf1as:
I am not sure if this problem has already been submitted but how do
I define two APIs, one that is supported from Leopard down and
another that is only supported in Snow Leopard if I only have one
binary for all OSes?
See
http://d
uary 23, 2010 10:09 AM
Subject: Deprecated APIs
Hello,
I am not sure if this problem has already been submitted but how do I define
two APIs, one that is supported from Leopard down and
another that is only supported in Snow Leopard if I only have one binary
Hello,
I am not sure if this problem has already been submitted but how do I define
two APIs, one that is supported from Leopard down and
another that is only supported in Snow Leopard if I only have one binary for
all OSes?
Below is a snippet of my code
// below should be performed if the OS
14 matches
Mail list logo
