Such a check is known from other programming languages (Java, C# etc.), and it would be great to have it in ABAP, too: Static methods should only be called on the class (=>), NOT on an instance (->), because if someone calls a static method on an instance, they probably don't know what is really happening. (I just discovered such a case in our code which was copied a lot to other places; a check would have helped to discover this: CL_FARR_TD_UTILITY_FACTORY=>CREATE_DOUBLE( )->INJECT_ITSELF( … ) is called, but INJECT_ITSELF is a class-method.) Grassau, Joerg-Michael
lucasborin
commented
3 years ago
Such a check is known from other programming languages (Java, C# etc.), and it would be great to have it in ABAP, too: Static methods should only be called on the class (=>), NOT on an instance (->), because if someone calls a static method on an instance, they probably don't know what is really happening. (I just discovered such a case in our code which was copied a lot to other places; a check would have helped to discover this: CL_FARR_TD_UTILITY_FACTORY=>CREATE_DOUBLE( )->INJECT_ITSELF( … ) is called, but INJECT_ITSELF is a class-method.) Grassau, Joerg-Michael