News for hackers. Stuff that matters.
Re:Torvalds: Standards are paper. I use paper to wipe my but... by sbov on Saturday March 26, 2011 @12:24PM (#2372468)
Pretty hard. C is a minefield of undefined behavior. Integer overflow is considered undefined behavior. Which means its perfectly valid to call abort(), wipe your hard drive, then light your system on fire. Or, have the number quietly wrap around.

Oh, and its perfectly fine for me to change the behavior from one to the other, or even have a lookup table of random responses to undefined behavior. Because, like, you're not following the standard. And its so easy.

Re:Torvalds: Standards are paper. I use paper to wipe my but... by haberman on Saturday March 26, 2011 @02:42PM (#2372802)
> C is a minefield of undefined behavior. Integer overflow is considered undefined behavior.

Only for signed integers. Unsigned integers are defined to wrap around.

Re:Torvalds: Standards are paper. I use paper to wipe my but... by yuhong on Saturday March 26, 2011 @03:38PM (#2372968)
Yea, I remember the joke about gcc #pragma once causing something like rogue to run.
Re:Torvalds: Standards are paper. I use paper to wipe my but... by jpr on Saturday March 26, 2011 @12:41PM (#2372513)
For what it's worth, I agree. Every time I hear about problems that arise from programming in C, with its undefined behaviour etc., I think to myself, there must be a better way to do it. But I don't know of any way that wouldn't involve scrapping 90%+ of software we use every day.