bad_alloc in new

[George2]

Hello everyone,


I usually check whether there is bad_alloc thrown to identify whether the allocation is success or not.

My question is,

Is there a way to disable bad_alloc and just to check the returned pointer NULL or not to identify allocation success or not -- which from function point of view, is as correct as the way to catch bad_alloc? Windows platform/Visual Studio is ok. I always see code does not check bad_alloc and just check the return pointer.

(My solution is to select Enable C++ Exception to No in Code Generation option in Visual Studio, not sure whether it is the most correct way.)


thanks in advance,
George

[Savage]

Hello everyone,


I usually check whether there is bad_alloc thrown to identify whether the allocation is success or not.

My question is,

Is there a way to disable bad_alloc and just to check the returned pointer NULL or not to identify allocation success or not -- which from function point of view, is as correct as the way to catch bad_alloc? Windows platform/Visual Studio is ok. I always see code does not check bad_alloc and just check the return pointer.

(My solution is to select Enable C++ Exception to No in Code Generation option in Visual Studio, not sure whether it is the most correct way.)


thanks in advance,
George

Yes,goggle for no throw new

[weaknessforcats]

Windows platform/Visual Studio is ok. I always see code does not check bad_alloc and just check the return pointer.

Yeah, that's Microsoft. They never outgrew C.

[George2]

Thanks Savage,


1.

You mean using std::nothrow?

2.

No need to link with nothrownew.obj in order to use std::nothrow?

Yes,goggle for no throw new

regards,
George

[George2]

Thanks weaknessforcats,


Any comments for my post #4?

Yeah, that's Microsoft. They never outgrew C.

regards,
George

[weaknessforcats]

Read your Stroustrup.

The nothrow new:

int* arr = new (nothrow)[100];
 

will return 0 when there is no heap.

Bjarne says this is to allow applications with pre-exception coding (read relic code) to compile and execute by checking for NULL on the return from new instead of having to change the application to accommodate bad_alloc.

That means you do not write new code using nothrow.

[George2]

Thanks weaknessforcats!


My question is anwered. And from your reply, I think there is no need to link with nothrownew.obj.

Read your Stroustrup.

The nothrow new:

int* arr = new (nothrow)[100];
 

will return 0 when there is no heap.

Bjarne says this is to allow applications with pre-exception coding (read relic code) to compile and execute by checking for NULL on the return from new instead of having to change the application to accommodate bad_alloc.

That means you do not write new code using nothrow.

regards,
George