Re: Why do we use -fobjc-arc instead of removing code with #define?
Re: Why do we use -fobjc-arc instead of removing code with #define?
- Subject: Re: Why do we use -fobjc-arc instead of removing code with #define?
- From: Dave DeLong <email@hidden>
- Date: Mon, 25 Jun 2012 18:41:21 -0700
Yes, you can do this, because ARC is a compile-time option and files are compiled individually.
To compile with ARC, you'll need to use the -fobjc-arc flag.
Cheers,
Dave
Sent from Jane
On Jun 25, 2012, at 6:20 PM, Graham Cox <email@hidden> wrote:
>
> On 26/06/2012, at 7:42 AM, Greg Parker wrote:
>
>> We recommend each file be written for either one or the other, with no attempt to be ARC-agnostic.
>
>
> Does this imply that ARC can be adopted gradually?
>
> For example, I have a large project that uses manual memory management. If I add a new class to it, can I write that class with ARC without having to adopt it for the whole project? I've been able to do that with properties and other Obj-C 2.0 stuff very successfully, but it wasn't clear that ARC could be managed the same way. If it can be done, how is ARC enabled for a specific class?
>
>
> --Graham
>
>
> _______________________________________________
>
> 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
_______________________________________________
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