Well, i am not so savy about threads as most people here, but i think my opionion is middle ground. I think that threads should not be used on C user applications as is, because of the low level implementation of threads and mutexs there. Instead if you realy need threads you should use some library that simplifies things. A textbook solution would suggest using "Monitor" objects. In essence, the cost for performance using low level impelementations is indeed to high. If performance is not your main requirement, i suggest you use JAVA 2.0 code, which handles threads very well, using behind the scene objects locks and calls to notify() as a variation to the singal-wait/signal-continue scheme. This would prevent any deadlocks (but not eliminate starvation completely, actually thats your only concern :) and would simplify debugging, not to mention the safe environment you are using. But again, you will loose performance.
* - * - * Tzahi Fadida [EMAIL PROTECTED] Fax (+1 Outside the US) 240-597-3213 * - * - * - * - * - * - * - * - * - * ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
