In ticket #207 dynamic sized arrays were removed, because they are not allowed according to the standard. Now, it was decided to allow them nevertheless because they are needed for the integration of TRDP into AUTOSAR/AP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here is some more background to the decision:
The dynamic size arrays in PD are not introduced due to a need in AUTOSAR/AP. They are introduced to support the design of FOC (Function Open Coupling) interfaces. They are needed to save band with so not all consist has to send status telegrams with fixed size arrays of the works case size. For example a train can be 1 cst with 20 doors or 32 cst with 4 doors. With static arrays the worst case size 20 of the status array most always be used.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ticket #207 undone; memory allocation, if data size increases
In ticket #207 dynamic sized arrays were removed, because they are not allowed according to the standard. Now, it was decided to allow them nevertheless because they are needed for the integration of TRDP into AUTOSAR/AP.
Here is some more background to the decision:
The dynamic size arrays in PD are not introduced due to a need in AUTOSAR/AP. They are introduced to support the design of FOC (Function Open Coupling) interfaces. They are needed to save band with so not all consist has to send status telegrams with fixed size arrays of the works case size. For example a train can be 1 cst with 20 doors or 32 cst with 4 doors. With static arrays the worst case size 20 of the status array most always be used.
Tested in api_test_4.c test5