Comments on: Multithreading Brings Joy http://wantonhubris.com/blog/2008/02/03/multithreading-brings-joy/ My work on display for the world to see. And possibly ignore. Fri, 10 Oct 2008 21:29:25 +0000 http://wordpress.org/?v=2.6.2 By: Warren http://wantonhubris.com/blog/2008/02/03/multithreading-brings-joy/#comment-343 Warren Mon, 04 Feb 2008 12:36:50 +0000 http://wantonhubris.com/blog/2008/02/03/multithreading-brings-joy/#comment-343 Sure. To be fair, the multithreading that I've added so far is stuff that sort of fell into my lap. I didn't plan for it to one day become multithreaded. Most if it was happy accidents (<em>"Hey, this routine doesn't depend on anything and I'm calling it once for every texture. Score!</em>"). But armed with these classes I'll be able to plan for it in the future and that should be pretty great. Sure. To be fair, the multithreading that I’ve added so far is stuff that sort of fell into my lap. I didn’t plan for it to one day become multithreaded. Most if it was happy accidents (“Hey, this routine doesn’t depend on anything and I’m calling it once for every texture. Score!“).

But armed with these classes I’ll be able to plan for it in the future and that should be pretty great.

]]> By: nevyn http://wantonhubris.com/blog/2008/02/03/multithreading-brings-joy/#comment-342 nevyn Mon, 04 Feb 2008 12:13:22 +0000 http://wantonhubris.com/blog/2008/02/03/multithreading-brings-joy/#comment-342 I've been coding for a few years, but not that much multithreaded code, so I always find it difficult to make logical designs that encapsulate that threading. More than two threads + transforming non-threadsafe code into what you *hope* is threadsafe = headache... But I agree with Mark: NSOperation really helps that design process. I had a horrible gc interaction bug, but after working around that, it works great. I’ve been coding for a few years, but not that much multithreaded code, so I always find it difficult to make logical designs that encapsulate that threading. More than two threads + transforming non-threadsafe code into what you *hope* is threadsafe = headache… But I agree with Mark: NSOperation really helps that design process. I had a horrible gc interaction bug, but after working around that, it works great.

]]>