[Scummvm-devel] PROPOSAL: Removing (f)printf usage

[yotam barnoy]

> Yes, handling error by bailing out / crashing is not a good way. Engines should instead check better for error conditions, and try to handle them as gracefully as possible, e.g. by returning to the launcher, showing a dialog, etc.
>
> But this is not something we can address by any piece of generic code. And there will always remain some errors that an engine cannot handle. So, no matter what, we need a way to handle fatal errors. The best we can do is to not call exit() directly, but at least allow the backend to try to "crash land the plane" as good as possible. Which is what we are trying to do here.
>

Oh gotcha. Sorry. What I meant to say was that we should strive to
have 2 types of error functions in the common code - fatal and
non-fatal. One would call OSystem::fatalError and one wouldn't. But
that's not OSystem API related, so sorry for hijacking the thread :)

Yotam