On Thu, 16 Nov 2006, TH & CD Maher wrote:
What situation would require the use of a thread? As in there is absolutely no other way to write this code or if it is coded without threads the code will take a million years to execute.
Very small low weight / low power consumption Embedded device without an MMU is why we using them. Given more grunt and embedded linux I would jump to processes immediately. One point to add, as one of the guys I work with keeps pointing out... Partitioning tasks into threads/processes has one and only one purpose. To enable tasks with different real time latency requirements to meet their deadlines. That's where the other posters comment about Gui responsiveness fits in. And yes, if he designed it properly, ie. With the business logic seperated from the UI, processes instead of threads would work fine. John Carter Phone : (64)(3) 358 6639 Tait Electronics Fax : (64)(3) 359 4632 PO Box 1645 Christchurch Email : [EMAIL PROTECTED] New Zealand
