> Currently, -Wsign-compare will warn if conditional operands differ in > signedness. This patch will move this warning to -Wmixed-sign-conditional >
What exactly are the semantics of mismatched sign types in a conditional expression? Is one of the arguments silently forced into (signed or unsigned) of the same size? Would it be possible to catch that coercion as a general case, rather than looking at the conditional operator specifically? [I suppose the -Wsign-conversion warning that Chandler mentioned would be the user facing equivalent of this. Then my question becomes: Can that warning be implemented in a general way such that there's no need to do specific work for the conditional operator case]
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
