[fpc-devel] volatile variables

Vinzent Höfler JeLlyFish.software at gmx.net
Tue Jun 28 20:34:44 CEST 2011

On Tue, 28 Jun 2011 20:09:18 +0200, Hans-Peter Diettrich  
<DrDiettrich1 at aol.com> wrote:

> When you have a look at TThreadList.LockList/UnlockList, then you'll see  
> that LockList enters the critical section, and UnlockList leaves it. All  
> code executed in between such two calls is absolutely ignorant of the  
> state of the CS, there is no in/outside.

Of course, why should it bother? The call to "unlock" should ensures  
memory synchronisation is required.


More information about the fpc-devel mailing list