We need to have proper error handling throughout the stack so errors can be detected and handled.
One example is when we fail to load a game (#149); the user should be sent back to the load game screen - at present there's not much we can do to provide that kind of experience.
This will require work to be able to shunt errors between Python and C++; as well as handling throughout both Python and C++.
Considerations:
C/C++ side can use error code returns or exceptions
While I personally don't care for Exceptions; given our integration with Python it's probably best to standard on Exceptions in both. This would also mean moving much of our C methods over to being more C++ oriented.
This would also enable more capabilities with finding issues.
We need to have proper error handling throughout the stack so errors can be detected and handled. One example is when we fail to load a game (#149); the user should be sent back to the load game screen - at present there's not much we can do to provide that kind of experience.
This will require work to be able to shunt errors between Python and C++; as well as handling throughout both Python and C++.
Considerations:
While I personally don't care for Exceptions; given our integration with Python it's probably best to standard on Exceptions in both. This would also mean moving much of our C methods over to being more C++ oriented.
This would also enable more capabilities with finding issues.