2 ms·
Errr, not really. "If you detached a thread in your application using a non-Cocoa API, such as the POSIX or Multiprocessing Services APIs, this method could st
by PaulDavisThe1st 2y ago
Errr, not really.
"If you detached a thread in your application using a non-Cocoa API, such as the POSIX or Multiprocessing Services APIs, this method could still return NO."
Also, I've never heard of this behavior despite years developing for macOS (admittedly tangentially). I don't see how that could work given that threads can come and go during the life of the application.
- saagarjha 2y agoYes, really: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Multithreading/CreatingThreads/CreatingThreads.html#//apple_ref/doc/uid/10000057i-CH15-125024-BAJGFJED https://developer.apple.com/library/archive/documentation/Co.... This also outlines what you have to do if you use POSIX threads.
- PaulDavisThe1st 2y agoInteresting. Definitely a 3rd approach that threads the needle between what win32 and X Window chose. Thanks for the link. [ EDIT: not quite sure how to think about this ... if I create NSThreads to act as worker threads that do not make cocoa calls, I still have to deal with new overhead in any cocoa call stacks. That's not ideal, but again, it's a "middle-way" approach, and like every other approach has its own pros and cons. ]