Re: Block Confusion...
Re: Block Confusion...
- Subject: Re: Block Confusion...
- From: R <email@hidden>
- Date: Tue, 31 Jan 2012 15:49:53 -0800 (PST)
David,
Class B is a parser. It is passed NSData to parse (weak reference)
and the Array (weak reference) from Class A. The results of the Data
parse are placed into the Array. Class A will be around for the life
of the application. Class B will be released (set to nil) after
completing the parse.
I chose this approach rather than delegation.
Thoughts?
On Jan 31, 11:25 am, David Duncan <email@hidden> wrote:
> On Jan 31, 2012, at 9:05 AM, R wrote:
>
> > never mind..... the class was getting dealloc. Still getting use to ARC and new ivar techniques.
>
> As a point of design here, without further knowledge on why your "ClassB" is keeping a weak reference to the target mutable array (rather than a strong one) this seems like a bad design choice. Weak references should generally be used in order to break retain cycles (and even then you still need to think carefully about where the weak pointer should go in such a design).
>
> Given the statements about your design, it seems like there are probably better ways for you to put the whole thing together, primarily as it seems you are trying to setup a producer-consumer pattern.
> --
> David Duncan
>
> _______________________________________________
>
> 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