|> case (int) SIG_DFL:
Assuming I'm thinking of the right bit of code, Fred was paraphrasing the
code. The "int" is actually an eCos typedef set by the hardware
abstraction layer so _will_ be correct for the hardware.
The problem is imbedded in SIG_DFL, the int cast above is simply to
get the older compiler to accept my test example.
SIG_DFL is typically something like:
#define SIG_DFL ((__sighandler_t)0)
and __sighandler_t is:
typedef void (*__sighandler_t)(int);
Indeed, but if explicitly cast to an integral type then it doesn't matter
what the intermediate expressions were surely?