• 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:10:51 +0100


We very rarely need hardware access or in fact any low level access
of any kind, and as such, I suspect that a much stronger type system
could be used.

Not sure I understand the logical connection in the above sentence.

The connection I'm making is that if we need hardware access we generally need access to write to a block of memory and don't generally know what abstract structure that memory represents. Hence in this situation it's generally a good idea to have an extremely weak type system, so that we can express such things.


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. It is therefore useful to be able to tell the computer at least some of these constraints, and have it check them for it's self.

I will repost this thread in the objective-C language thread and perhaps we can carry on this discussion there.

Thanks

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


References: 
 >Objective-C and it's future (From: Thomas Davie <email@hidden>)
 >Re: Objective-C and it's future (From: "Shawn Erickson" <email@hidden>)

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