Kagamin Wrote: > One can get rid of OOM just by adding a couple of lines to the default > malloc, that call custom handler (similar to onOutOfMemoryError handler) wich > does any magic wanted, so OOM doesn't break nothrow functions, and if it's > thrown, this means that recovery code has failed to recover and application > exits. So nothrow protocol remains the same.
I think, preventing OOM is the only possible technique to make sure you don't interfere with the rest of the application.
