• 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: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?


  • Subject: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
  • From: Gregory Wieber <email@hidden>
  • Date: Fri, 7 Jan 2011 10:03:45 -0800

That kind of ignores the point of everything else I wrote,  and is splitting hairs on wording.  The word 'overhead' was meant to refer to any and all performance issues related to using objective-c in a render callback.  

On Fri, Jan 7, 2011 at 9:20 AM, Paul Davis <email@hidden> wrote:
On Fri, Jan 7, 2011 at 11:58 AM, Gregory Wieber <email@hidden> wrote:
> You want your render callback code to be as efficient as possible,  and that
> means that the overhead of calling objective-c messages can come into play.
>  That said, objective-c messages are not always going to be your bottleneck,
>  because it's easy to do something else in your code that's 10x's worse than
> using a few simple objective-c messages.  But if you're unsure of the gritty
> details,  then just avoid them altogether.

the issue is not the "inefficiency" of objective C versus anything
else. its that the objective C runtime can block.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
      • From: Paul Davis <email@hidden>
    • Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
      • From: Paul Davis <email@hidden>
    • Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
      • From: Kyle Sluder <email@hidden>
    • Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
      • From: Gregory Wieber <email@hidden>
References: 
 >Do I really need to steer clear of Objective-C when providing data for RemoteIO? (From: Morgan Packard <email@hidden>)
 >Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO? (From: Brian Willoughby <email@hidden>)
 >Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO? (From: Gregory Wieber <email@hidden>)
 >Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO? (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
  • Next by Date: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
  • Previous by thread: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
  • Next by thread: Re: Do I really need to steer clear of Objective-C when providing data for RemoteIO?
  • Index(es):
    • Date
    • Thread