Test and test-and-set: Difference between revisions

Revision as of 15:06, 12 October 2012

Revision as of 14:59, 4 February 2015

Line 27:

==Caveat==

Although this [[Optimization (computer science)|optimization]] is useful in [[system programming]] it should be avoided in high level [[concurrent programming]] unless all constraints are clear and understood. One example of bad usage is a similar [[programming idiom|idiom]] called [[double-checked locking]], which, isunder listedcertain asconditions, can be an [[anti-pattern]].<ref>David Bacon et al. [http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html The "Double-Checked Locking is Broken" Declaration].</ref>

==See also==