Split nameCollectorHandler for multiple languages #38
Description
As we add more languages to srcML, the differences between languages' use of user defined names causes the complexity of the handler to grow. Python's collection logic has resulted in a lot of one-off if-statements that wrap all of the previous code, and then the code for Python.
In particular is the printing logic, which has been duplicated numerous times. This can be fixed, but will be a bandaid fix and not actually address the underlying design issue.
We should look into splitting nameCollectorHandler apart to compartmentalize the logic for different language types - i.e., no declaration/no typed languages (Python) vs declaration/typed (C,C++,C#,Java). Emphasis should be on supporting the future additions of languages (JavaScript, Swift, etc.)