• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSData (again!)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSData (again!)


  • Subject: NSData (again!)
  • From: Pascal Goguey <email@hidden>
  • Date: Sat, 14 Dec 2002 23:32:58 +0900

Hello!

Summary of the history:
The other day, I asked a question about how to subclass NSData
from the interface builder. I got a few replies (thanks again), and learned
about forwardInvocation which is a very nice concept. All the replies
I got were telling me that "I should not subclass NSData" or "I probably
don't want to subclass NSData".

I guess it is probably true, that there is probably a good technical reason
to prefer wrapping to inheritance, otherwise the people who wrote
Project Builder and Interface Builder would have enabled the possibility
to subclass NSData.

Now, what I need to know is WHY it is bad practice to subclass.
There are some subclass (e.g. NSApplocation inherits from NSResponder).
So why should my class not inherit NSData, but only wrap it?

Thanks,

Pascal
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: NSData (again!)
      • From: Joe Osborn <email@hidden>
References: 
 >Re: NSData (From: Mike Shields <email@hidden>)

  • Prev by Date: Re: Help me please to find a job in Cocoa
  • Next by Date: Re: How to toggle the subviews of a split view?
  • Previous by thread: Re: NSData
  • Next by thread: Re: NSData (again!)
  • Index(es):
    • Date
    • Thread