On Oct 22, 2005, at 3:08 PM, Robert Tillyard wrote: > On 22 Oct 2005, at 18:07, TjL wrote: > >> ...... Original Message ....... >> On Sat, 22 Oct 2005 02:55:26 -0700 "Philip J Robar" >> <pjrobar at areyoureallythatstupid.org> wrote: >> >>>> All OSX-native apps are multi-threaded and thus benefit from any >>>> multi-proc system. >>> >>> Umm, no they're not. Applications must be explicitly coded to use >>> multiple threads. This is a non-trivial task. >> >> are Apple apps? That's what I first read this to imply (all >> native Apple >> apps vs OSX apps). >> >> I have heard it said in the past that only some apps *should* be >> coded to >> use multiple threads. > > From memory I though that all Cocoa apps run the GUI in a separate > thread, UI elements like progress bars are normally animated in a > separate thread. I'm not a Cocoa programmer, yet, so I stand corrected on this. But this isn't quite the same as what I think was implied by the post I was responding to. Yes, there's a separate thread handling your GUI requests, but there's no magic going on which makes the actual work being done by any single application take advantage of multithreading and multiple processors. This has to be done by the programmer. Phil