DIP62: Volatile type qualifier for unoptimizable variables in embedded programming

[John Colvin via Digitalmars-d]

On Thursday, 17 July 2014 at 15:58:05 UTC, Andrei Alexandrescu 
wrote:
> I think an approach based on functions peek/poke is a lot more 
> promising. D programs must define sequences of std calls 
> anyway, otherwise even the simplest programs that use 
> writeln("What's your name?") followed by a readln() are 
> incorrect. So in a way peek/poke come for "free".

Could you expand on this "sequences of calls"? What exactly do 
you mean by defining it?