It wasn't until Java 5 that this issue was understood and fixed. Now the volatile keyword prevents problematic reordering of reading and writing ...
確定! 回上一頁