Given is the following code:
Does the function declaration of myCallbackFunction in the above code comply with the Rule 8.2?
As the prototype specifies the parameters by usage of the type my_callback_fct_t and this prototype includes all the parameter and their names I would treat this as a correct prototype as requested by Rule 8.2. even though this is not explicitly listed as being compliant in the MISRA standard.
The background for this kind of function prototyping is to tie the function to an externally defined function prototype which will be used for callbacks in another part of the code.
kind regards
sowiso
Code:
myheader.h
/* define a type of a callback function */
typedef uint16_t(my_callback_fct_t)(uint16_t const *a);
myimplementation.c
#include "myheader.h"
/* function declaration of myCallbackFunction */
static my_callback_fct_t myCallbackFunction;
[...]
/* function definition of myCallbackFunction */
static uint16_t myCallbackFunction(uint16_t const *a)
{
return (*a) + (uint16_t)1u;
}Does the function declaration of myCallbackFunction in the above code comply with the Rule 8.2?
As the prototype specifies the parameters by usage of the type my_callback_fct_t and this prototype includes all the parameter and their names I would treat this as a correct prototype as requested by Rule 8.2. even though this is not explicitly listed as being compliant in the MISRA standard.
The background for this kind of function prototyping is to tie the function to an externally defined function prototype which will be used for callbacks in another part of the code.
kind regards
sowiso