Suppose foo is a variable of type long. The following operation is not an atomic operation:<\/p>\n
\r\nfoo = 65465498L;\r\n<\/pre>\nIndeed, the variable is written using two separate operations: one that writes the first 32 bits, and a second one which writes the last 32 bits. That means that another thread might read the value of foo, and see the intermediate state.<\/p>\n
Making the operation atomic consists in using synchronization mechanisms in order to make sure that the operation is seen, from any other thread, as a single, atomic (i.e. not splittable in parts), operation. That means that any other thread, once the operation is made atomic, will either see the value of foo before the assignment, or after the assignment. But never the intermediate value.<\/p>\n
A simple way of doing this is to make the variable volatile:<\/p>\n
\r\nprivate volatile long foo;\r\n<\/pre>\nOr to synchronize every access to the variable:<\/p>\n
\r\npublic synchronized void setFoo(long value) {\r\n this.foo = value;\r\n}\r\n\r\npublic synchronized long getFoo() {\r\n return this.foo;\r\n}\r\n\/\/ no other use of foo outside of these two methods, unless also synchronized\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Suppose foo is a variable of type long. The following operation is not an atomic operation: foo = 65465498L; Indeed, the variable is written using two separate operations: one that writes the first 32 bits, and a second one which writes the last 32 bits. That means that another thread might read the value of… Continue reading