Jonas Maebe wrote:
On 07 Oct 2013, at 11:33, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
[interlocked increment/decrement]
They do not include any memory barrier. The only thing those routines
guarantee on all platforms, is that the value is atomically
incremented/dec
On 07 Oct 2013, at 11:33, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
[interlocked increment/decrement]
They do not include any memory barrier. The only thing those routines
guarantee on all platforms, is that the value is atomically
incremented/decremented.
(btw th
Jonas Maebe wrote:
On 07 Oct 2013, at 09:14, Mark Morgan Lloyd wrote:
Benito van der Zander wrote:
In the end I stuck in code to increment/decrement a counter, and
looked for it to be explicitly 0 or 1.
Do you need to put a memory barrier around that, or does the critical
section take care
In our previous episode, Jonas Maebe said:
> > I used the interlocked increment/decrement, which- as I understand
> > it- should handle membar itself on architectures that can benefit
> > from it.
>
> They do not include any memory barrier. The only thing those routines
> guarantee on all pl
On 07 Oct 2013, at 09:14, Mark Morgan Lloyd wrote:
Benito van der Zander wrote:
In the end I stuck in code to increment/decrement a counter, and
looked for it to be explicitly 0 or 1.
Do you need to put a memory barrier around that, or does the
critical section take care of that?
I used
Benito van der Zander wrote:
In the end I stuck in code to increment/decrement a counter, and
looked for it to be explicitly 0 or 1.
Do you need to put a memory barrier around that, or does the critical
section take care of that?
I used the interlocked increment/decrement, which- as I unde
In the end I stuck in code to increment/decrement a counter, and
looked for it to be explicitly 0 or 1.
Do you need to put a memory barrier around that, or does the critical
section take care of that?
On 10/06/2013 06:55 PM, Mark Morgan Lloyd wrote:
Michael Van Canneyt wrote:
On Sun, 6
On Sun, 6 Oct 2013, Mark Morgan Lloyd wrote:
Michael Van Canneyt wrote:
On Sun, 6 Oct 2013, Mark Morgan Lloyd wrote:
Is there a preferred way of reading back whether something (including the
current thread) has already entered a TCriticalSection?
To my knowlede this does not exist.
The M
Michael Van Canneyt wrote:
On Sun, 6 Oct 2013, Mark Morgan Lloyd wrote:
Is there a preferred way of reading back whether something (including
the current thread) has already entered a TCriticalSection?
To my knowlede this does not exist.
The Microsoft implementation of a critical section has
On Sun, 6 Oct 2013, Mark Morgan Lloyd wrote:
Is there a preferred way of reading back whether something (including the
current thread) has already entered a TCriticalSection?
To my knowlede this does not exist.
The Microsoft implementation of a critical section has TryEnterCriticalSection,
Is there a preferred way of reading back whether something (including
the current thread) has already entered a TCriticalSection?
I'm trying to put assertions in code that, partly under non-GUI thread
control via Synchronize, adds and deletes pages to a TPageControl. If I
do this
property Bl
11 matches
Mail list logo
