Friendly-C

[deadalnix via Digitalmars-d]

On Friday, 29 August 2014 at 21:03:59 UTC, Ola Fosheim Grøstad
wrote:
> On Friday, 29 August 2014 at 19:37:28 UTC, deadalnix wrote:
>> NULL or any address, as you can change memory protection on a 
>> per
>> page basis, and have different protection for read write and
>> execution.
>
> If your semantics require page faults to trap then you should 
> declare the storage volatile.
>

Or what ? Or it is undefined behavior ?