Re: Why does ARC retain method arguments even with full optimization?
Re: Why does ARC retain method arguments even with full optimization?
- Subject: Re: Why does ARC retain method arguments even with full optimization?
- From: Charles Srstka <email@hidden>
- Date: Sat, 05 Nov 2011 13:23:37 -0500
On Nov 5, 2011, at 1:18 PM, Wade Tregaskis wrote:
>>> Note that (so far as Mac OS X is concerned - I don't know about iOS) this only happens with the 64-bit runtime on Intel, on Lion. Previous runtimes don't even have this optimisation, and there's somewhat surprisingly no 32-bit implementation of the critical callerAcceptsFastAutorelease().
>>
>> That’s true, in the sense that ARC itself is not supported on the old runtime at all, let alone optimizations related to it.
>
> "ARC is supported in Xcode 4.2 for Mac OS X v10.6 and v10.7 (64-bit applications) and for iOS 4 and iOS 5. Weak references are not supported in Mac OS X v10.6 and iOS 4."
>
> http://developer.apple.com/library/ios/#releasenotes/ObjectiveC/RN-TransitioningToARC/_index.html
Right. Notice the (64-bit applications) qualifier. If you try to build for 32-bit, it’ll be the old runtime, and the compiler will give you an error if you have ARC turned on.
Charles_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden