16-10-2018, 10:10 AM
1. The working-group agrees that the first paragraph of the rationale needs amending. It should refer to implementation behaviour (C99 J.3.7(1)), not alignment issues or undefined behaviour.
2. The working-group agrees the rationale does not apply to a conversion to intptr_t/uintptr_t. The group will review casts to intptr_t/uintptr_t in a later release. It is permissible to convert between void* and intptr_t/uintptr_t if you write a deviation to the rule.
3. Thank you for your comment.
The Advisory/Required categories for the rule 11.X rules are planned to be reviewed as part of future work on the MISRA C guidelines.
2. The working-group agrees the rationale does not apply to a conversion to intptr_t/uintptr_t. The group will review casts to intptr_t/uintptr_t in a later release. It is permissible to convert between void* and intptr_t/uintptr_t if you write a deviation to the rule.
3. Thank you for your comment.
The Advisory/Required categories for the rule 11.X rules are planned to be reviewed as part of future work on the MISRA C guidelines.
Posted by and on behalf of the MISRA C Working Group