• 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: ObjC 2.0 Class +encodeWithCoder:
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC 2.0 Class +encodeWithCoder:


  • Subject: Re: ObjC 2.0 Class +encodeWithCoder:
  • From: Jens Miltner <email@hidden>
  • Date: Mon, 25 Feb 2008 15:53:13 +0100


Am 21.02.2008 um 23:57 schrieb Jean-Daniel Dupas:

No. Every where you can provide an instance, you should be able to provide a Class to.
For example, it's perfectly legal to register a Class as a notification observer (and use a Class method as target).
It also perfectly legal to register a Class as a delegate and implements Class method instead of instance methods to handle message.

Hmmh - but what exactly do you expect the class method endodeWithCoder: to do?
It's a class method, so it can't encode an instance.
Do you really want to encode the class object itself?




An Class method is just an instance method of the Class Object.

Le 21 févr. 08 à 22:32, Charles Steinman a écrit :

Class methods are prefixed with a +, and I don't think
there ever was a documented +encodeWithCoder: method
of NSObject or any other class, so it looks like it
was simply a quirk of the runtime that this ever
worked at all.

Cheers,
Chuck

--- "A.M." <email@hidden> wrote:

I have a DO-based application which uses a Class
object as a root
proxy under 10.4- it works as expected. Objective-C
2.0 seems to have
broken this option because Class no longer responds
to -
encodeWithCoder:.

I am not able to think of a reason for this
regression, but perhaps
the new dynamic nature of Classes prevents my
use-case.

Is this a genuine regression or should I have never
relied on passing
Classes as root proxies?

Thanks.
-M
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:


This email sent to email@hidden




____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
_______________________________________________


Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: ObjC 2.0 Class +encodeWithCoder:
      • From: Jean-Daniel Dupas <email@hidden>
References: 
 >Re: ObjC 2.0 Class +encodeWithCoder: (From: Charles Steinman <email@hidden>)
 >Re: ObjC 2.0 Class +encodeWithCoder: (From: Jean-Daniel Dupas <email@hidden>)

  • Prev by Date: Re: Garbage Collection makes my app look fat
  • Next by Date: Re: Observing with GC
  • Previous by thread: Re: ObjC 2.0 Class +encodeWithCoder:
  • Next by thread: Re: ObjC 2.0 Class +encodeWithCoder:
  • Index(es):
    • Date
    • Thread