Engine Exceptions

Classes
class	Mochi::EngineError
	Generic error that can be thrown inside the MochiEngine. More...
class	Mochi::ResourceNotFoundError
	Specific implementation of EngineError for resources that are not found in the specified path. More...
class	Mochi::SystemInitializationError
	Specific implementation of EngineError for subsystems that have not been initialized correctly. More...
class	Mochi::MalformedInputAction
	Specific implementation of EngineError thrown when actions loaded by an Input::IActionManager are malformed. More...
class	Mochi::AudioOperationError
	Specific implementation of EngineError thrown when there is an error on the audio subsystem. More...

Detailed Description

List of exception classes thrown in the engine.

Errors thrown on the setup phase terminate the application, as they are considered errors that one can not recover from (like a core asset not being loaded, or a submodule not being setup correctly).

Errors thrown while on the update phase are to be checked manually and continue the execution or report a "false" as a return in the update in order to finish execution. Any EngineError without a explicit type (any inheriting from it) will terminate the application anyway. If your code can throw any error, catch that specific error or the game will crash.