Is it safe to use sharedptr to act as Uobject hard reference?

[Commander_Shepard]

Is it safe to do something like the following ( don’t ask why :p) :

TSharedPtr<UObject>(NewObject<MyObjectClass>(SomeOwner));

or are smart pointers only for non uobjects and every Uobject derived class should be maintained exclusively only by reflection system?

[ExtraLifeMatt]

Limitations

• Shared pointers are not compatible with Unreal objects (UObject classes)!

Unreal Smart Pointer Library

There is a TWeakObjPtr you can use to store a weak uobject reference, but otherwise have to go through the UPROPERTY system.

[BrUnO_XaVIeR]

No, don’t do that.
We have TWeakObjectPtr<> for that case.

I don’t know if that TSharedPtr<UObject> would even compile. When I tried some year ago, Unreal just said “no!”

[Balgy]

@Commander_Shepard

Is it safe to do something like the following ( don’t ask why :p) :

TSharedPtr<UObject>(NewObject<MyObjectClass>(SomeOwner));

or are smart pointers only for non uobjects and every Uobject derived class should be maintained exclusively only by reflection system?

Unreal uses a garbage collection system to do its memory management, so you can also take advantage of that.

If there is a fundamental need for your object to not be destroyed, there is a way to add an object to GC’s root set: https://api.unrealengine.com/INT/API…oot/index.html