🚀 go-pugleaf

"Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket> wrote:
>I am confused by the two critical sections.  What am I missing?
>
>I understand the idea is to block reading of a value that has been only
>partially altered.  Would it not work if a critical section were only
>established for that code which modifies the variable?

If both threads works asynchronously - one modifies when want, 
another reads when want then no need any critical sections and 
semaphors for both threads.

But may be second thread (read) must tracks any changes of variable. It is another case. And then semaphors can be a good solution.


As I understand critical section do not block access to 
sharing variable. Only code inside critical section is blocked. 
Another thread of the same process can't enter in the blocked critical critical section. So if threads can access to variable from critical section they do it by turn without conflicts.
Really no need to use it when one thread modify and another 
only read (it can be useful only if some threads make modifications).

So my answer was incorrect.

By the way. I search in Borland site and find no reference 
about Borland C# Builder product. I something missed and Borland 
does not sell and support it.

Vladimir.