MX2 has a real problem with transparency. In effect everything is grouped together and the compiler sorts out the dependancies for you (great by the way). But it makes debugging and code following virtually impossible without constant help (nagging). The c++ or even old blitz way of doing things is a much better (in my opinion) way of doing things. E.G.
You can’t reference anything without importing it in the file.
E.G.
I am working ion mainwindow.monkey2. How do I know what it’s dependant files are?
I can’t actually compile this file in any way without compiling the file that calls it and has the file references!
There really should some sort of implicit header file or dependants import in mainwindow.monkey2 to show what it’s dependants are and how it is constructed?
help or suggestions on this?
It’s certainly making monkey2 a real ‘pain in the butt’ to program. If users are going to ‘want’ to adopt this as a language, then transparency and ease of use should be the key here?