• 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: Why RunLoop?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why RunLoop?


  • Subject: Re: Why RunLoop?
  • From: Bill Bumgarner <email@hidden>
  • Date: Mon, 16 May 2011 14:45:04 -0700

In short, do **not** poll.  Not ever.

If you are doing something like this:

	while (stillDontGotIt) {
              sleepForAMomentAndHopeWeGetIt();
        }

(or the obvious spin-and-try-lock variant).

Then you are doing it wrong.

It eats CPU, makes your app less responsive, eats battery life, and is less efficient.   Far far more efficient is to set up various triggers or points of coordination -- queues, callbacks, run loop events, etc… -- through which your app will be notified when something is ready to be processed.

b.bum_______________________________________________

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: Why RunLoop?
      • From: Bing Li <email@hidden>
References: 
 >Why RunLoop? (From: Bing Li <email@hidden>)

  • Prev by Date: Asynchronous Notification Failed
  • Next by Date: Re: Asynchronous Notification Failed
  • Previous by thread: Re: Why RunLoop?
  • Next by thread: Re: Why RunLoop?
  • Index(es):
    • Date
    • Thread