If uninitialised memory is accessed as an array of unsigned char, that's actually OK -
unsigned char can't have any trap values. I don't know which type is being used here.
Posted May 15, 2008 21:39 UTC (Thu) by Ross (subscriber, #4065)
[Link]
While that gets rid of the likely causes of actual errors, I beleive it still violates the
standard, and a compiler is free to do whatever it wants in that situation.