• 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: Cocoa et al as HCI usability problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa et al as HCI usability problem


  • Subject: Re: Cocoa et al as HCI usability problem
  • From: glenn andreas <email@hidden>
  • Date: Fri, 23 May 2008 16:21:34 -0500


On May 23, 2008, at 3:49 PM, Sherm Pendley wrote:

The implementation of foreach appears almost expressly designed to better
support scripting languages. The ObjC foreach() syntax is just chrome - the
"fast" comes from under the hood. It compiles down to a single method that's
called to get a count of items and a C array of ids. For a scripting bridge,
an opportunity to replace several trips across the bridge per iteration with
a single round trip for the whole array is *huge*.



I actually consider the "for each" to be the "stealth viral" feature (much like "//" style comments were with C++).


After having used them in an ObjC 2.0 project, I hate the thought of turning back to the old "declare yet another enumerator, while (ugly expression that's also a statement)" style in pre-ObjC 2.0.

While properties are nice, it's the "for each" thing that really is thing I miss most when not working in ObjC 2.0... (if only the equivalent NSEnumerator based loop were automatically generated in non ObjC 2.0)


Glenn Andreas email@hidden <http://www.gandreas.com/> wicked fun! m.o.t.e.s. | minute object twisted environment simulation



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Cocoa et al as HCI usability problem
      • From: "Michael Ash" <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: "Sherm Pendley" <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: Bill Bumgarner <email@hidden>
References: 
 >Re: Cocoa et al as HCI usability problem (From: Jeff LaMarche <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Andy Lee <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Jeff LaMarche <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Andy Lee <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: "Sherm Pendley" <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Andy Lee <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Graham Cox <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: Ilan Volow <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: GĂ©rard Iglesias <email@hidden>)
 >Re: Cocoa et al as HCI usability problem (From: "Sherm Pendley" <email@hidden>)

  • Prev by Date: Re: Can't get file type code using [fileAttr valueForKey:NSFileHFSTypeCode]
  • Next by Date: Re: A documetation suggestion (was Re: Cocoa et al as HCI usability problem)
  • Previous by thread: Re: Cocoa et al as HCI usability problem
  • Next by thread: Re: Cocoa et al as HCI usability problem
  • Index(es):
    • Date
    • Thread