Re: Processes vs. Threads in Cocoa software architectures
Re: Processes vs. Threads in Cocoa software architectures
- Subject: Re: Processes vs. Threads in Cocoa software architectures
- From: John Stiles <email@hidden>
- Date: Wed, 6 Sep 2006 14:51:05 -0700
On Sep 6, 2006, at 2:45 PM, Shawn Erickson wrote:
You either value memory protection or you don't.
As soon as you have ONE thread in your process your can screw up your
own processes memory just as bad as you could with multiple threads.
I agree; multiple threads don't increase your chances of stomping
memory. It's just not an issue.
There are certain classes of bugs that show up more in threaded apps,
but I wouldn't consider memory stomping to be in that list. Usually
it's timing-sensitive bugs that get worse—and often it's bugs that
would have happened either way, but the threading makes the problem
happen more quickly, which is actually a good thing from a debugging
perspective.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden