# Why I must use Execute\_FunctionName in interfaces?

**URL:** <https://forums.unrealengine.com/t/why-i-must-use-execute_functionname-in-interfaces/373335>\
**Category:** UI\
**Tags:** interfaces, calling-a-function, usability, unreal-engine, feedback, question, CPP\
**Created:** [October 14, 2016, 12:45pm UTC](https://forums.unrealengine.com/t/why-i-must-use-execute_functionname-in-interfaces/373335 "2016-10-14T12:45:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![broly](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@broly](https://forums.unrealengine.com/u/broly)\
**Post date:** [October 14, 2016, 12:45pm UTC](https://forums.unrealengine.com/t/why-i-must-use-execute_functionname-in-interfaces/373335/1 "2016-10-14T12:45:30Z")

</div>

It’s so awkward to use this  
`IMyInterface::Execute_MySuperGetter(MyObj);` instead of `MyObj->MySuperGetter();`

Maybe first variant is better to use? Why this?

I request first variant for BlueprintNativeEvents.

Thanks!
