Re: thread priorities?

Actually, they should definitly always be advisory. You can't easily write a portable program that depends on either priorities working or fairness for correctness, you would write your code differently in each case. And schedules are intimately tied to an implementation so I wouldn't want to straightjacket them. so, people can use priorities for performance reasons, but never for correctness ones no matter what the concurrency implementation. (unless, of course, a particular implementation gives stronger promises than the standard) John -- John Meacham - ⑆repetae.net⑆john⑈