On 6/1/2017 7:48 AM, H. S. Teoh via Digitalmars-d wrote:
Yes. Saving *after* a crash was detected is stupid, because you no longer can guarantee the user data you're saving hasn't already been corrupted. I've experienced over-zealous "crash recovery" code in applications overwrite the last known good copy of my data with the latest, most up-to-date, and also most-corrupted data after it detected a problem. Not nice at all.
An even better idea is to use rolling backups, with the crash recovery backup only being the most recent, not the only, version.
