-
Key: DDSPSMC11_-7
-
Status: open
-
Source: Real-Time Innovations ( Mr. Alejandro Campos)
-
Summary:
Conditions have an optional functor handler that WaitSet::dispatch() calls when they're active. But the ways to set this handler vary depending on the Condition type:
Condition type How you set the handler GuardCondition handler(Functor&) setter (therefore mutable) ReadCondition In constructor (therefore immutable) QueryCondition No way to set it (it seems a oversight; should be same as ReadCondition) StatusCondition No way to set it (not clear if it's on purpose or an oversight) Note that making the handler mutable or immutable has consequences in the thread-safety requirements of the implementations.
-
Reported: DDS-PSM-Cxx 1.0b2 — Thu, 21 Jul 2016 22:35 GMT
-
Updated: Wed, 15 May 2019 12:24 GMT
DDSPSMC11_ — Inconsistent ways to set functor in Condition types
- Key: DDSPSMC11_-7
- OMG Task Force: DDS-PSM-Cxx v1.1 RTF