Home/ Questions/Q 66919
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T19:10:43+00:00

I’m working on a large, aging code base for an MFC app. The code

  • 0

I’m working on a large, aging code base for an MFC app. The code has been worked on by many developers over time, and as a result, we have three different ways throughout the code of dealing with the possibility of an allocation failure with new.

The first way is to test for NULL on the result of new. We don’t use nothrownew.obj so this is clearly an error that needs to be cleaned up.

The second is to catch CMemoryException* (yes, C++ exceptions are enabled in the compiler). From what I understand, MFC overrides the standard operator new, and throws this thing instead. I am fairly certain that this second method is correct in the MFC application itself. MFC overrides new, with its strange CMemoryException throwing version.

The last comes from our base of people who are good with C++, but aren’t neccessarily MFC programmers. They are catching const std::bad_alloc&.

What I really don’t know is what to expect for static libraries linked into the application. This is were the vast majority of the code that uses bad_alloc lives. Assuming these libraries are not compiled with MFC or ATL, and are written in standard C++ only, can they expect to catch bad_alloc? Or will the presence of MFC in the application they link to infect them with the global new operator and render their attempts to fail cleanly on a bad allocation moot?

If you have an answer, could you explain how this works, or point me to the right reference to sort this out?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. It will depend on the compile options for the static libraries to be linked to the application.

    If the libraries are compiled with a configuration to use the static Standard C++ run-time then I would expect the operator new from the Standard C++ run-time to be called.

    If libraries are compiled with a configuration to use the Standard C++ run-time DLL then the resolution of these functions will be delayed until program load and should be resolved to the MFC replacements of operator new.

    I also included a link to this Herb Sutter article regarding handle allocation errors that you may find useful.

    • 0