Re: operator new not forced to throw std::bad_alloc?

Ian Collins wrote:

>> void* __cdecl operator new(size_t nSize)
> 
> That (__cdecl) makes the function non-standard, so all bets are probably
> off at this point.

I think you're mixing up "standard" and "****table" here. A particular
implementation can use any amount of its own folklore provided it allows
to compile standard-conforming code. As long as the operator is found
for code assuming the signature as given in the standard, the
implementation is conforming. On the other hand, a particular
implementation is not required to compile in another environment. I
don't see the problem here.

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