*phew* I'd just written some code to
test the "setPriority" behaviour and was worried about my understanding when I say the priority changing.
I guess K&B mean the JVM will not, for its own reasons, change the priority of a thread; they way it might, for its own reasons, yank a thread back to the Runnable pool or ignore "yield()".