G
Gordon Burditt
The worst thing that can happen is that the programmer _does_ write to
"possible minor data corruption", especially the kind you don't
notice, is about the worst case possible. You finally realize
what's happening, and then you discover that last year's backups
are corrupted and you've lost lots of work.
Remind me never to fly on any airplanes with your software running
them.
Remember, anything can run in zero time and zero memory if you don't
require the result to be correct.
the end of the mallocated block. In this case, either there's a SIGSEGV
again (no worse off than before), or if the 512Kb is in the middle of
the heap malloc() is drawing from then the writes might well succeed,
and the program can continue albeit with some possible minor data
corruption.
"possible minor data corruption", especially the kind you don't
notice, is about the worst case possible. You finally realize
what's happening, and then you discover that last year's backups
are corrupted and you've lost lots of work.
Remind me never to fly on any airplanes with your software running
them.
Remember, anything can run in zero time and zero memory if you don't
require the result to be correct.