Re: Are memory safety and maximized data volatility mutually exclusive?

You can, to a certain extent, adopt the programming style of 
C/Assembler for your critical data. Store it is a byte array. 
When done with it, overwrite it. If the compiler decides the 
overwrite code isn't needed and removes it, then overwrite it 
with data and perform arithmetic on that data and find a way to 
write the result to the outside world. (Or use assembler to 
overwrite. Or use less optimization in your compile.)

The extra CPU/memory bandwidth cost of fooling the compiler is 
probably trivial compared with the total cost of running the application.

Cheers - Bill

-----------------------------------------------------------------------
Bill Frantz        | Concurrency is hard. 12 out  | Periwinkle
(408)356-8506      | 10 programmers get it wrong. | 16345 
Englewood Ave
www.pwpconsult.com |                - Jeff Frantz | Los Gatos, 
CA 95032