Topic Types generated from IDL that contain enums are not bounded. The instantiation of these types only calls the annotation constructor of the member class and there's no chance to set the type code. I'm not sure if this is done on purpose due to serialization or if there's no way to bound enums.
Would it be possible to set each EnumMember typecode to the parent EnumTypeCode? I believe this just results in the default bounding being true.
Is there an issue with serializing the enums that prevents this bounding? I wouldn't think so as C++ doesn't really care about enum types if they are implemented as a standard integer (which I believe is being done when the pubsubtypes are generated).
Topic Types generated from IDL that contain enums are not bounded. The instantiation of these types only calls the annotation constructor of the member class and there's no chance to set the type code. I'm not sure if this is done on purpose due to serialization or if there's no way to bound enums.
Would it be possible to set each EnumMember typecode to the parent EnumTypeCode? I believe this just results in the default bounding being true.
Is there an issue with serializing the enums that prevents this bounding? I wouldn't think so as C++ doesn't really care about enum types if they are implemented as a standard integer (which I believe is being done when the pubsubtypes are generated).