> Le 27 févr. 2018 à 01:06, Matt Ingalls <[email protected]> a écrit : > > I have to admit that in the past i’ve done some dubious things inside the > audio thread -- and i’m not proud of it.. ;) > > But in some recent C++ work, I'm not letting myself call any function I’m not > absolutely sure is lock-free. > > Ross Bencina’s article is still my go-to-reference: > http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing > > <http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing> > > But now I’m wondering if I’m being too anal... > > Could I at least call memcpy and memset?
I hope they are safe on an audio thread as calls to theses functions are generated by the compiler. So even if you don’t call them yourself, you may end up with code that use them.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
