[Exceptional C++ Style] Item 23: To new, Perchance to throw, Part 2: Pragmatic Issues in Memory Management

[Jez Higgins]

> 
>> Recovering from memory exhausting sensibly is difficult - one of our 
>> most basic resources has run out after all - and unwinding the stack 
>> is generally the best option.
> 
> And hoping nothing else begs for memory en-route causing a second 
> exception.

Go directly to terminate, do not pass go - hence the item's references 
to attempting to unwind.

Jez


--- StripMime Report -- processed MIME parts ---
multipart/signed
  text/plain (text body -- kept)
  application/pgp-signature
---