From: adebaene on
Hello all,

Browsing around MSDN online, I stumped upon some new functions :
SleepConditionVariableCS, SleepConditionVariableSRW,
WakeAllConditionVariable and WakeAllConditionVariable...

Does anyone know anything about these? I couldn't find anything about
them except their (empty and useless for now) entry in MSDN).
So it seems we will have CondVars available on the next version? And
what does SRW stands for? Something about Reader-Writer lock I
suspect...

Thanks for any light....

Arnaud
MVP - VC

From: Tom Widmer [VC++ MVP] on
adebaene(a)club-internet.fr wrote:
> Hello all,
>
> Browsing around MSDN online, I stumped upon some new functions :
> SleepConditionVariableCS, SleepConditionVariableSRW,
> WakeAllConditionVariable and WakeAllConditionVariable...
>
> Does anyone know anything about these? I couldn't find anything about
> them except their (empty and useless for now) entry in MSDN).
> So it seems we will have CondVars available on the next version? And
> what does SRW stands for? Something about Reader-Writer lock I
> suspect...

There's InitializeSRWLock, AcquireSRWLockExclusive, AcquireSRWLockShared
and Release functions as well, so I suspect you are right in all your
assumptions. Presumably locking "shared" is for readers, and "exclusive"
for writers.

Tom
From: Pavel Lebedinsky [MSFT] on
This is correct. Hopefully the docs will improve in time for beta2,
but the doc writer for this area is overloaded so it might take
longer.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Tom Widmer [VC++ MVP]" wrote:

>> Browsing around MSDN online, I stumped upon some new functions :
>> SleepConditionVariableCS, SleepConditionVariableSRW,
>> WakeAllConditionVariable and WakeAllConditionVariable...
>>
>> Does anyone know anything about these? I couldn't find anything about
>> them except their (empty and useless for now) entry in MSDN).
>> So it seems we will have CondVars available on the next version? And
>> what does SRW stands for? Something about Reader-Writer lock I
>> suspect...
>
> There's InitializeSRWLock, AcquireSRWLockExclusive, AcquireSRWLockShared
> and Release functions as well, so I suspect you are right in all your
> assumptions. Presumably locking "shared" is for readers, and "exclusive"
> for writers.