Klever

The most reliable way is to use for process labels primitive types or pointers for more complicated types only. So I am going to implement casts to pointers for labels of all non-pointer complicated types. By the way additionally I will add automatic includes of header files given in interface categories specifications and if there are given then EMG will not do mentioned above casts. The latter case example is interrupt enum type which is used for interrupt return values and including of a corresponding header is a better solution.

I would like to warn you to include additional headers very accurately, otherwise we will fall back into related #6560. I suggest that you can safely include appropriate headers if they are really required for corresponding interfaces in corresponding files. In particular you can specify required headers for corresponding interfaces directly in environment model specifications rather than include them unconditionally.

In addition using pointers instead of, say, structures can also fail since you will need at least corresponding structure declarations (something like struct A;) while they can absent without including corresponding headers.

Idealy, we should be able to detect whether the structure is defined, declared or not. Based on this we should use the type itself, pointer to a type or void* correspondingly.
For now as far as we mostly use in specifications parameters and return values which are pointers to a declared structure type or simple type, the fix for #7262 should solve most of the cases.

Since I cannot detect absence of a declaration in an entry point file, I am going to declare additionally all structures and unions to avoid warnings from a compiler.