|
![](/i/fill.gif) |
jhu wrote:
> Your implication is that GCC is inferior to what I'm guessing is Code
> Warrior, which is not always the case.
What do you expect when you compare a multi-threaded GUI program to a
single-threaded terminal application? A terminal application compiled with
CodeWarrior will absolutely be faster, but after all, that was my point from
the beginning: The Mac OS X GUI eats away the processing power very
effectively. Naturally more so when you actually have a GUI application that
has to update status displays while rendering. The rendering for the GUI
application also has to run in a different thread. Of course, (by default)
both get the same time slice, just that the GUI version is burdened running
several GUI-related threads in the same time slice, while the terminal
application runs only one thread.
Thorsten
Post a reply to this message
|
![](/i/fill.gif) |