My point is that proper programming discipline would have prevented the
problem from arising in the first place. It would be far more appropriate
for kernel programmers to exercise such discpline than to treat them like
babies, breaking well-known syntax in the process.
It seems trivial to pick up all potential min/max problems with the Stanford
Checker in the case some programmer has been too clueless to think about
their code as they write it. A simple policy statement for users of min/max
would have avoided this entire mess.
Not that I you're going to back down, it just made me feel better to get this
off my chest ;-)
-- Daniel - 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/