Kick Spy!, Kick Zeitgeist and Kick Widgets
blogs.msdn.com — That part I knew… what we news to me is there is a better way to do volatile, and that is with an explicitly memory barrier before accessing the data member.. We have a an API for that: System.Threading.Thread.MemoryBarrier(). This is more efficient than using volatile because a volatile field requires all accesses to be barriers and this effects some performance optimizations. read more...
haacked.com — Why locking on "this" can be a bad idea -- and how to lock in a safer manner. read more...
Sponsored Link: www.carlist.ie
Ads by The Lounge