Pure functions in interfaces

[anonymous_user_4fe9f58b1 (anonymous_user_4fe9f58b)]

@kamrann;227864

I believe I’m right in saying that your second line there is superfluous. This cast will, I think, actually fail in the case that the interface is implemented purely in your blueprint (as opposed to your blueprint deriving from a native class which itself implements the interface).

You’re absolutely right. But using it in this fashion makes the calling method more consistent with non-Event function calls. In fact, it started out this way until I hit the check telling me to use the Execute thunk:

	UBlueprintBaseClass* Blueprint = GetThatBlueprint();
	IHasProbabilityCurveInterface* Probability = InterfaceCast<IHasProbabilityCurveInterface>( Blueprint );
	const UCurveFloat* Curve = Probability->GetProbabilityCurve();

In this particular context, I am not null checking the result of the interface cast because the blueprint getter I am using is guaranteed to return a blueprint class that implements that interface. It is, in essence, a tacky way of doing multiple inheritance for a highly modular blueprint base.