undefined | Better HN

0 pointsPaulDavisThe1st1y ago0 comments

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.

0 comments

saagarjha1y ago

Yes, really: https://developer.apple.com/library/archive/documentation/Co.... This also outlines what you have to do if you use POSIX threads.

PaulDavisThe1stOP1y ago

Interesting. 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. ]

j / k navigate · click thread line to collapse

0 comments

saagarjha1y ago

Yes, really: https://developer.apple.com/library/archive/documentation/Co.... This also outlines what you have to do if you use POSIX threads.

PaulDavisThe1stOP1y ago

Interesting. Definitely a 3rd approach that threads the needle between what win32 and X Window chose. Thanks for the link.

j / k navigate · click thread line to collapse