• 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: choice of thread API for audio feeder purposes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: choice of thread API for audio feeder purposes


  • Subject: Re: choice of thread API for audio feeder purposes
  • From: Kurt Revis <email@hidden>
  • Date: Wed, 26 Mar 2003 21:56:17 -0800

On Wednesday, March 26, 2003, at 04:58 PM, Kurt Bigler wrote:

I see from postings to this list that some people are using pthreads, and
then using other lower-level mach thread apis to do things like setting
thread priority, etc. But then why not just use the lower-level api in the
first place? (But I have not found it yet.)

Because it's generally easier to drop down to the lower-level API only when you have to.

I have seen NSThreads, for example in Kurt Revis's PlayBufferedSoundFile
project, but for the moment want to avoid introducing Objective-C into my
project just in order to create threads.

Certainly. NSThreads are just a wrapper on top of pthreads. There's no reason to go out of your way to use an NSThread if you aren't in a Cocoa app.

I have heard of something called cthreads, but don't know if they are around
any more.

cthreads were the old threading package on OpenStep and (maybe) very early versions of OS X (before 10.0). They've been completely replaced by pthreads now. I don't know what vestiges of cthreads are still in the system but they can be safely ignored.

I have been wading through the developer.apple.com
documentation, and have found it pretty difficult to even find out what the
available thread api's are,

Have you seen this? I think it may answer some of your questions...
http://developer.apple.com/technotes/tn/tn2028.html

I certainly do find it to be a struggle to wrest information from the developer website, and I
guess I haven't found a strategy for finding documentation that really works.

I find that the search box works pretty well for me (it does a Google search of everything on the site). But perhaps I just know what to search for.

Otherwise, the best way to get Apple to do something about the docs is to tell them:
http://developer.apple.com/techpubs/techpubsfeedback.html

--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >choice of thread API for audio feeder purposes (From: Kurt Bigler <email@hidden>)

  • Prev by Date: Re: AU - CW code gen problems
  • Next by Date: Re: Using getrusage function in a CoreAudio callback
  • Previous by thread: Re: choice of thread API for audio feeder purposes
  • Next by thread: Re: choice of thread API for audio feeder purposes
  • Index(es):
    • Date
    • Thread