> But then again, how do you know it's the type of x we want, maybe we want
> type of y, that is and signed char (not an int like x).
> Talk about hidden buffer overflow stuff :)
This is one of the big problems with min and max, you get deeply suprising
and unpleasant results if you don't consider sign propogation, sizes and
overruns carefully. In C there are some great evils in that area, and its
one reason a lot of people prefer to write such code explicitly.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:01:01 EST