The situation with the INT_RANGE_OVERFLOW check is similar, except
there the macro is more like this:

 #define a 2147483647
 #define b 1
 #define FOO (INT_ADD_OVERFLOW (a,b) ? INT_MAX : (a)+(b))
 int i = FOO;

Again, any compiler that warns about potential overflow of
2147483647+1 should be ignored, because the expression
2147483647+1 cannot possibly be evaluated.

Ok. I read the intprops.h file and I agree with this example. 
Pity there is no other (simpler) way to handle this.

Thanks for the explanations.

Fabrice




--
Fabrice Popineau
-----------------------------
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
------------------------------