It looks like macro works just like a function with extra ability to have execution pins. Feels like we should just use macro for everything.
Is there any reason we want to use function over macros?
Macros stored in blueprint classes can’t be called from outside, unless they’re in a macro library.
Functions, on the other hand, can.
Oh ok thanks.
I think when I build a game for real, I will go for creating countless macro libraries so it’s more versatile.
another difference I see is macro don’t have this const/pure stuff from the “pure vs impure functions” lecture
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.