On Jul 13, 2009, at 12:41 PM, Quincey Morris wrote:
What you *don't* get for free from subclassing is an internal storage mechanism -- you have to invent that for yourself (usually by putting a real NSArray instance variable in your subclass :) ). You also need a pretty clear understanding of how class clusters work, and that's where confusion can set in.
These two sentences are exactly my point. Perhaps we have differing opinions of what makes an angry, fire-breathing, treasure-grubbing dragon. :-)
Perhaps another, more universal analogy that I didn't make up just now: The devil is in the details.
What's more (said in an off-list discussion with the OP): It's just not worth it to say "give me a mutable array with a single instance of a certain class".
-- I.S. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
