> I would suggest that this is a case where there's no reason MAME shouldn't just do > the right thing: if there's any kind of non-filesystem related reason a diff chd > doesn't open (version mismatch, damaged header, whatever), delete it and create a new > one. Obviously if some error comes back from the underlying OS (bad path or I/O error > or whatever) then you'd show a message and halt.
It doesn't do that because you may want to keep/upgrade the contents of the DIFF. There may be high scores or other data you want kept, so just deleting it isn't a viable option. And renaming + silently upgrading it isn't great either because you won't know what happened or why changes you made are suddenly gone.
|