🚀 go-pugleaf

In article <1993Jan7.221207.13818@leland.Stanford.EDU> dkeisen@leland.Stanford.EDU (Dave Eisen) writes:
[...]
>This has nothing to do with malloc. The hypothetical compiler
>could simply insert this error checking information whenever
>it does a conversion from a (void *) to a (struct foo *). Again,
>the basic question is still unresolved here: can a conversion
>from one pointer type to another affect bytes other than those
>where the pointer variable is stored?

Which directly brings up the question if (or if not) for
any modifiable lvalue `x' and some `y' of the same type an
assignment
			x = y;
may behave differently
as a bitwise copy
			memcpy(&x, &y, sizeof x);

(For the pedantics: Assume the appropriate header is included
and the two objects do not overlap.)

To put it into the language of the standard: May some (otherwise
strictly conforming) program change its behavior if the above
two were switched.
-- 
Martin Weitzel, email: martin@mwtech.UUCP, voice: 49-(0)6151-6 56 83