• 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: Re: Objective-C and it's future
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: Objective-C and it's future


  • Subject: Re: Re: Objective-C and it's future
  • From: "Shawn Erickson" <email@hidden>
  • Date: Fri, 7 Jul 2006 18:25:24 -0700

On 7/7/06, Damien Sorresso <email@hidden> wrote:
On 7 Jul, 2006, at 8:07 PM, Shawn Erickson wrote:
> ...but the point is you could implement classes that are specific
> about what they return (I often do that with my init methods) and the
> compiler would flag this for you.

But you must also remember that this only works for classes *you*
write. You cannot statically type Apple's classes in the way you
would if they were written in C++ because, without any exception I'm
aware of, all their `init' methods return the `id' type.

Obviously. _______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: Objective-C and it's future (From: Damien Sorresso <email@hidden>)
 >Re: Re: Objective-C and it's future (From: "Shawn Erickson" <email@hidden>)
 >Re: Objective-C and it's future (From: Damien Sorresso <email@hidden>)

  • Prev by Date: Re: Re: Objective-C and it's future
  • Next by Date: Re: Objective-C and it's future
  • Previous by thread: Re: Objective-C and it's future
  • Next by thread: Re: Objective-C and it's future
  • Index(es):
    • Date
    • Thread