Could a 'new' statement fail without throwing an exception?

Question

Consider the following code snippet:

try{
LibObject* obj = new LibObject();
if (!obj)
    return 0;
}catch(...){
    return 0;
}
return 1;

I don't know the implementation of the LibObject since it comes from an external library.

Generally speaking, could have any sense to check if the new object instance (obj) is NULL? Or the check is simply unuseful?

Could a new statement return a NULL object without throwing an exception?

possible duplicate of [Will new return NULL in any case?](http://stackoverflow.com/questions/550451/will-new-return-null-in-any-case) — user4815162342, Feb 25 '15 at 11:29

score 1 · Accepted Answer · edited Feb 25 '15 at 12:06

1

LibObject* obj = new LibObject();

Don't use parenthesis here. And if you don't want alloc exception, you should use std::nothrow

LibObject* obj = new(std::nothrow) LibObject;
if (obj == nullptr) return 0;
else return 1;

This is the correct syntax. You can find a reference here:

edited Feb 25 '15 at 12:06

HolyBlackCat

answered Feb 25 '15 at 11:47

amchacon

What if the exceptions are disabled? – user1095108 Feb 25 '15 at 12:08
@user1095108 If you disable the exception, new will return null_ptr instead – amchacon Feb 25 '15 at 12:15
So you really need to use that syntax for every new statement in your code? I've never seen it before, maybe because memory allocation it's being trusted... – ABCplus Feb 25 '15 at 12:40
@ABCplus it's a example. I would use a new without try/catch (and let abort the program if i don't have enough memory). – amchacon Feb 25 '15 at 12:46

1 Answers1