Re: Blocks and Methods...
Re: Blocks and Methods...
- Subject: Re: Blocks and Methods...
- From: R <email@hidden>
- Date: Sat, 28 Jan 2012 13:16:53 -0800 (PST)
To all,
Thanks for taking the time to post advice..... I think I now
understand much better! --Ron
On Jan 28, 12:50 pm, R <email@hidden> wrote:
> That is precisely what is giving me the confusion. If retained the
> received block in a NSMutableArray, the block should stick around (via
> a strong array pointer) for another method. It only stays around if I
> equate the block to a typedef variable and then put that variable in
> the array. I'm using ARC.
>
> On Jan 28, 9:51 am, Ken Thomases <email@hidden> wrote:
>
>
>
>
>
>
>
>
>
> > On Jan 28, 2012, at 10:40 AM, R wrote:
>
> > > I originally chose to hold the block in an array, but that failed.
> > > I'm still confused over that...
>
> > By itself, an array only retains the block. A block must be explicitly copied if it is to outlive the scope that created it. And, of course, that copy operation has to be balanced with an eventual release.
>
> > Regards,
> > Ken
>
> > _______________________________________________
>
> > 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
>
>
> > 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
>
>
> 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