New (std::nothrow) vs. New within a try/catch block

by

Consider what you are doing. You’re allocating memory. And if for some reason memory allocation cannot work, you assert. Which is more or less exactly what will happen if you just let the std::bad_alloc propagate back to main. In a release build, where assert is a no-op, your program will crash when it tries to access the memory. So it’s the same as letting the exception bubble up: halting the app.

So ask yourself a question: Do you really need to care what happens if you run out of memory? If all you’re doing is asserting, then the exception method is better, because it doesn’t clutter your code with random asserts. You just let the exception fall back to main.

If you do in fact have a special codepath in the event that you cannot allocate memory (that is, you can actually continue to function), exceptions may or may not be a way to go, depending on what the codepath is. If the codepath is just a switch set by having a pointer be null, then the nothrow version will be simpler. If instead, you need to do something rather different (pull from a static buffer, or delete some stuff, or whatever), then catching std::bad_alloc is quite good.

More Related Contents:

  1. How do exceptions work (behind the scenes) in c++
  2. Measuring exception handling overhead in C++
  3. If you shouldn’t throw exceptions in a destructor, how do you handle errors in it?
  4. How to overload std::swap()
  5. Does C++ support ‘finally’ blocks? (And what’s this ‘RAII’ I keep hearing about?)
  6. Why is my program slow when looping over exactly 8192 elements?
  7. What is the efficient way to count set bits at a position or lower?
  8. Virtual functions and performance – C++
  9. Throwing exceptions from constructors
  10. Why should exceptions be used conservatively?
  11. Should I use an exception specifier in C++?
  12. How can I measure CPU time and wall clock time on both Linux/Windows?
  13. Why are Python Programs often slower than the Equivalent Program Written in C or C++?
  14. Is there any guarantee of alignment of address return by C++’s new operation?
  15. Getting an accurate execution time in C++ (micro seconds)
  16. Can the use of C++11’s ‘auto’ improve performance?
  17. How much footprint does C++ exception handling add
  18. Will C++ exceptions safely propagate through C code?
  19. A fast method to round a double to a 32-bit int explained
  20. Exception Error c0000005 in VC++
  21. Is accessing data in the heap faster than from the stack?
  22. Throwing an exception from within a signal handler
  23. throw new std::exception vs throw std::exception
  24. What happens if a constructor throws an exception?
  25. Should I still return const objects in C++11? [duplicate]
  26. Speed difference between If-Else and Ternary operator in C…?
  27. C++ : handle resources if constructors may throw exceptions (Reference to FAQ 17.4]
  28. Multiple classes in a header file vs. a single header file per class
  29. Optimizing member variable order in C++
  30. Is it possible to map string to int faster than using hashmap?

Leave a Comment