Once semcode (after PR#50) is able to better deal with having multiple functions of the same name, it is not a large step to extend semcode functionality to cover object oriented languages, where every class is likely to have some functions of the same name, e.g. init in every Python class.
Adding support for object oriented languages can be built on top of handling, and being able to select, multiple functions of the same name.
Once semcode (after PR#50) is able to better deal with having multiple functions of the same name, it is not a large step to extend semcode functionality to cover object oriented languages, where every class is likely to have some functions of the same name, e.g. init in every Python class.
Adding support for object oriented languages can be built on top of handling, and being able to select, multiple functions of the same name.