• 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
Re: Confusing problems with inheritance in Objective-C
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Confusing problems with inheritance in Objective-C


  • Subject: Re: Confusing problems with inheritance in Objective-C
  • From: Chris Hanson <email@hidden>
  • Date: Tue, 22 Jun 2004 08:44:12 -0700

On Jun 21, 2004, at 11:03 PM, Darren Ford wrote:
I agree -- actually the reason for doing this way is that I want to use Cocoa's built-in property serialization class to be able to write an array of these 'objects' out to a file.

Why not implement NSCoding and use NSKeyedArchiver/NSKeyedUnarchiver for your serialization?

Another common strategy is to implement a pair of methods to get a dictionary/plist representation for an instance and to initialize an instance from a dictionary/plist repreesntation.

-- Chris

--
Chris Hanson <email@hidden>
http://www.livejournal.com/users/chanson/
_______________________________________________
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.


References: 
 >Confusing problems with inheritance in Objective-C (From: Darren Ford <email@hidden>)
 >Re: Confusing problems with inheritance in Objective-C (From: Chris Hanson <email@hidden>)
 >Re: Confusing problems with inheritance in Objective-C (From: Darren Ford <email@hidden>)

  • Prev by Date: TIFF Error?
  • Next by Date: "Go to" widget in a TableView
  • Previous by thread: Re: Confusing problems with inheritance in Objective-C
  • Next by thread: NSColorWell, setColor and bindings
  • Index(es):
    • Date
    • Thread