On 9/12/15 10:48 PM, Prudence wrote:
It would seem to be the logical thing to do?
That is, suppose two threads are sharing a resource. Thread A has it
locked. B is "waiting". Is B in a loop burning cycles running in the
background(regardless of thread.sleep, which only alleviates the
problem)
It would seem to be the logical thing to do?
That is, suppose two threads are sharing a resource. Thread A has
it locked. B is "waiting". Is B in a loop burning cycles running
in the background(regardless of thread.sleep, which only
alleviates the problem) or does it yield completely and
