• 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: Future Objective-C changes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Future Objective-C changes


  • Subject: Re: Future Objective-C changes
  • From: Jim Rankin <email@hidden>
  • Date: Fri, 16 May 2003 17:59:31 -0400

I'm also in the "keep Objective-C elegant and simple" camp. I want a few simple to understand constructs that can interact in powerful ways. My feeling is that the more "features" you add to a language, the more ways the language can bite you in unexpected ways.

I thought the recent thread on memory management was a good example of this, where several people pointed out that garbage collection was a poor fit for many application domains as opposed to retain/release reference counting. Some people have pointed out in this thread, too, that adding "static language" type features to ObjC would break some of the cool, dynamic things you can do witht the language now.

Sometimes the best decision is to leave it alone.

IMHO,
-jimbo
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Future Objective-C changes
      • From: Gerard Iglesias <email@hidden>
References: 
 >Re: Future Objective-C changes (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Re: OT: WWDC
  • Next by Date: Hide the scrollbar track?
  • Previous by thread: Re: Future Objective-C changes
  • Next by thread: Re: Future Objective-C changes
  • Index(es):
    • Date
    • Thread