• 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: Gregory Weston <email@hidden>
  • Date: Fri, 7 Jul 2006 21:00:11 -0400

Thomas Davie wrote:

However, when we are dealing with much more abstract concepts such as
objects, we generally know what our data structures are.  We know how
they are going to be used, and we know what they should and should
not do.

But notice what you said there. Or what you didn't. You indicated that we know and care about _behavior_. Not structure, nor appearance, nor type. We just want to know that when we send "this message" we'll get a response that, itself, only needs to conform to certain behavior. We don't really want collections to be of certain specific types because there's no reason to restrict a collection to holding only one type of data. That may not be so obvious for a traditional integer-index array, but consider an associative array. I rarely want a dictionary in which _every_ key is a string and _every_ value is a numeric value.



_______________________________________________ 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: Thomas Davie <email@hidden>
  • Prev by Date: 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