On Tue, 2006-09-26 at 04:44 +0000, acahalan at gmail dot com wrote: > > Although it wouldn't work for the example code, extending the aliasing > behavior > of (char*) to (void*) would fix the problem for LOTS of code out in the wild. > People normally use a (void*) when they want a generic pointer type to play > casting games with. This is a case where the C standard is very far from the > reality of how people write code. The example code is fairly unusual.
But C aliasing is not based on pointers but on accesses so it is wrong to it that way. -- Pinski
