dds::core::policy::TypeConsistencyEnforcementKind_def Struct Reference

The definition of the dds::core::safe_enum TypeConsistencyEnforcementKind. More...

#include <PolicyKind.hpp>

Public Types
enum	type {   DISALLOW_TYPE_COERCION,   ALLOW_TYPE_COERCION,   AUTO_TYPE_COERCION }
	The underlying enum type. More...

Detailed Description

The definition of the dds::core::safe_enum TypeConsistencyEnforcementKind.

Member Enumeration Documentation

enum dds::core::policy::TypeConsistencyEnforcementKind_def::type

The underlying enum type.

Enumerator:

DISALLOW_TYPE_COERCION	The DataWriter and the DataReader must support the same data type in order for them to communicate. This is the degree of type consistency enforcement required by the OMG DDS Specification prior to the OMG Extensible and Dynamic Topic Types for DDS Specification.
ALLOW_TYPE_COERCION	The DataWriter and the DataReader need not support the same data type in order for them to communicate as long as the DataReader's type is assignable from the DataWriter's type. For example, the following two extensible types will be assignable to each other since MyDerivedType contains all the members of MyBaseType (member_1) plus some additional elements (member_2). struct MyBaseType { long member_1; }; struct MyDerivedType: MyBaseType { long member_2; }; Even if MyDerivedType was not explicitly inheriting from MyBaseType the types would still be assignable. For example: struct MyBaseType { long member_1; }; struct MyDerivedType { long member_1; long member_2; }; For additional information on type assignability refer to the OMG Extensible and Dynamic Topic Types for DDS Specification.
AUTO_TYPE_COERCION	This AUTO value will be applied as TypeConsistencyKind::DISALLOW_TYPE_COERCION when the data type is annotated with @transfer_mode(SHMEM_REF) while using C, Traditional C++, or Modern C++ APIs. In all other cases, this AUTO value will be applied as TypeConsistencyKind::ALLOW_TYPE_COERCION. [default]