Unfortunately I need to target Tiger also. Thanks for the info,
though, this will be useful to know in a year or so. ;)
Todd Ransom
Return Self Software
http://returnself.com
On Jun 2, 2008, at 12:32 PM, j o a r wrote:
On Jun 2, 2008, at 9:12 AM, Todd Ransom wrote:
It seems that what I need is a non-retaining array. I googled
around a bit and was surprised that I could not find an existing
implementation. It looks like I can create one by subclassing
NSMutableArray, overriding the primitive methods, and using a
CFArray as the backing store with NULL callbacks to avoid any kind
of retain or release when objects are added or removed. Still, I
thought I would ask around and see if anyone else has done this
before I embark on trying to subclass a class cluster.
Has anyone out there created a non-retaining array class or come up
with another solution to this problem? Or is there anything in
particular I should watch out for when subclassing NSMutableArray?
If you're only targeting Leopard or later, you might want to take a
look at "NSPointerArray".
j o a r
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
