On Wed, Apr 16, 2008 at 5:34 PM, John Stiles <[EMAIL PROTECTED]> wrote: > > Honestly, I can't see value in always coding to CFArray just so I can rip > out the back end later if I don't like the results.
The value is that 99% of the time you won't need to, saving time and effort by using a nice built-in class with reasonable performance. > If anything, it would make more sense to me to use NSArray for that > purpose, since I know working with and subclassing NSArray will be easy and > painless. Core Foundation is just ugly in comparison... :) I don't really follow. NSArray *is* CFArray. They are just two names for one entity, so you make a custom CFArray the same way you make a custom NSArray: subclass NS[Mutable]Array and override the primitive methods. It's just annoying to talk about NS/CFArray all the time so I picked one name and used it. Mike _______________________________________________ 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]
