It's nearly impossible to create such an application on OS X. Even a
simple application using the default Cocoa project in Xcode will
spawn multiple threads (the main thread and the UI thread).
In 10.5 I imagine it's going to be even more common. What with
CoreAnimatation and all the various changes to existing APIs to
improve performance.
I think currently the only way to guarantee you own all the threads
is to only use BSD APIs. But even then OS X might spawn new threads
for you.
Ack, at 3/12/07, James Bucanek said:
So this kind of thing is very common in multi-threaded DO
applications that are sending asynchronous messages in both
directions. But it shouldn't ever happen in a single thread/run-loop
environment.
--
Sincerely,
Rosyna Keller
Technical Support/Carbon troll/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
