Re: advice for becoming less clueless about thread safety?
Re: advice for becoming less clueless about thread safety?
- Subject: Re: advice for becoming less clueless about thread safety?
- From: Brian Lambert <email@hidden>
- Date: Sat, 17 Mar 2012 13:36:19 -0700
My two cents:
This is a good place to start:
https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Multithreading/Multithreading.pdf
Given your needs, pay special attention to the section on Synchronization starting on page 66.
On Sat, Mar 17, 2012 at 1:27 PM, Morgan Packard
<email@hidden> wrote:
Hello list,
So far, my approach to communication across the main thread and the RemoteIO callback thread has been... just access shared data (almost always float values) between threads willy nilly and hope for the best. This has worked well enough for me to create several entertaining and popular (if not rock-solid) pieces of software. I think it's time for me to get a bit more pulled together about all of this. I want to know just when it's safe to access the same piece of data from different threads without a mutek (never?), what the consequences of writing "unsafe" code are, what the consequences of using mutexes in a realtime thread are, when it's appropriate to use the OS's atomic operations and how to use them, and a bit more about just what the heck a thread really is anyway.
It seems like it's maybe time to spend some hours with a book. Maybe this one?
Any other advice on ways for me to become not totally clueless about threads?
thanks,
-Morgan
--
===============
Morgan Packard
aim: mpackardatwork
_______________________________________________
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
_______________________________________________
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