You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A game dev shouldn't be forced to catch both std::exception and Mezzanine::Exception::OutOfRange. We want to retain the benefits of having simple exceptions and a build system list of exceptions.
This should be easy to implement by changing AddJagatiException to accept a single item or a list. If it is passed a list then some simple manipulation should be able to split the list then write correct parameter lists and inheritance line.
The text was updated successfully, but these errors were encountered:
A game dev shouldn't be forced to catch both std::exception and Mezzanine::Exception::OutOfRange. We want to retain the benefits of having simple exceptions and a build system list of exceptions.
This should be easy to implement by changing AddJagatiException to accept a single item or a list. If it is passed a list then some simple manipulation should be able to split the list then write correct parameter lists and inheritance line.
The text was updated successfully, but these errors were encountered: