new in Objective-C in init - how to handle std::bad_alloc? - c++

Question

I need to wrap a c++ object inside an Objective-C class - initially I did that by putting the C++ objects inside the #implementation in the .mm file like this:
MyObjCClass.h:
#interface MyObjCClass : NSObject
#end
MyObjCClass.mm:
#implementation MyObjCClass {
MyCppClass member;
}
#end
Sadly I had to give this up since this code is also used in a project which targets 32-bit architectures and thus this feature is not supported. So I did a forward struct declaration, the struct is defined in the .mm file and wraps the C++ object:
MyObjCClass.h:
struct MyObjCClassPrivate;
#interface MyObjCClass : NSObject {
MyObjCClassPrivate* memberPrivate;
}
-(void)dealloc;
-(id)init;
#end
MyObjCClass.mm:
struct MyObjCClassPrivate {
MyCppClass member;
}
#implementation MyObjCClass
-(void)dealloc
{
delete memberPrivate;
memberPrivate = nullptr;
}
-(id)init
{
if (self = [super init])
{
memberPrivate = new MyObjCClassPrivate; // what happens if new throws std::bad_alloc ?
}
return self;
}
#end
The question is - should I care if the allocation with new fails? What are the consequences (apart from the exception being thrown?) - do I need to do some additional cleanup for the Ojbective-C class instance?
I dont want to put the c++ stuff in the header since this class is also used by plain Objective-C code, which then fails to compile.