Bug: C Caller block using Simulink.AliasType() for typedef'd C types produces type error in Reactis
| Submitted | Product | Status | ||
|---|---|---|---|---|
| 2023-05-26 | Reactis for Simulink | Resolved in 2022.2.2 (released Jun 30, 2023; release notes) | ||
|
If a C Caller block uses a "typedef" in C and a corresponding Simulink.AliasType() in Simulink, Reactis produces a runtime error saying "The data type or size of the block's output (...) does not match the connected signal " | ||||