@Mark_Yedinak wrote:
Overloading, which is not supported in LVOOP. If it were the OP would have his solution.
Overloading is mostly useful when your language can make templates. As long as you call those methods statically, the names might as well be different. If the interface is the same: use overriding, if not: use a different name. Or give them the same name with a different interface: just don't implement the method in the parent(s). This usually doesn't last as sooner or later you'll want to inherit the method.