operator new not forced to throw std::bad_alloc?

Hi!

During some debug session of an MFC application (VS2005) I found out
that std::allocator<double>::allocate calls operator new which throws
a
CMemoryException.

I expected operator new to throw std::bad_alloc, so that exception
went
uncaught. This is odd.

void* __cdecl operator new(size_t nSize)
{
....
  // That's platform specific code here:
  if (_afxNewHandler == NULL || (*_afxNewHandler)(nSize) == 0)
}


Q: Did I misunderstand Stroustrup?
Q: Is an STL allowed to throw things which do not inherit from
std::exception?
Q: No standard under my pillow: What's the wording about what operator
new may throw?


Markus

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]