tape block number is set at wrong place
Currently tape block number is reset in a thread which waits for mover continue event. In theory if there are n threads waiting for mover continue event then tape block number will be reset n-times. It should be reset in thread which emits mover continue event, because that's the thread which modifies mover state and other threads should access the modified state in read-only mode.
While it doesn't constitute a bug, it confuses readers of the code and from algorithmic point of view it's wrong and should be fixed.
Updated by Electric Monk almost 7 years ago
Author: Jan Kryl <firstname.lastname@example.org> 4738 tape block number is set at wrong place Reviewed by: Albert Lee <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>