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

Re: Objective-C and it's future


  • Subject: Re: Objective-C and it's future
  • From: Thomas Davie <email@hidden>
  • Date: Sat, 8 Jul 2006 01:42:59 +0100


On 8 Jul 2006, at 01:41, Shawn Erickson wrote:

On 7/7/06, Rob Ross <email@hidden> wrote:

I'm just learning Obj-C myself, so maybe my understanding is not
correct. But, don't you actually have the option to use static typing
in certain instances, and use dynamic typing in others?

Eg:

id      myStr;

vs

NSString *myStr;

Won't the second version give you the benefits of static typing
(compiler time checking)?

So my understanding is you can have the best of both worlds. Or have
I misunderstood something?

Correct.

That is correct, but can you specify for me an NSArray containing only items that respond to a specific display method?


This is the sort of check that I would like to be able to do at compile time.

Bob
_______________________________________________
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


  • Follow-Ups:
    • Re: Objective-C and it's future
      • From: Scott Thompson <email@hidden>
    • Re: Objective-C and it's future
      • From: Andrew Satori <email@hidden>
References: 
 >Objective-C and it's future (From: Thomas Davie <email@hidden>)
 >Re: Objective-C and it's future (From: Charlton Wilbur <email@hidden>)
 >Re: Objective-C and it's future (From: Rob Ross <email@hidden>)
 >Re: Re: Objective-C and it's future (From: "Shawn Erickson" <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: Re: Objective-C and it's future
  • Next by thread: Re: Objective-C and it's future
  • Index(es):
    • Date
    • Thread