Difference between revisions of "Intermediate C++ Game Programming Tutorial 22"

• • Examples of its usage in the Framework, a good practice for working with any API
  • Everytime a Direct 3D Function is called, the return value is checked for error codes and handled

• • Conventional error handling requires checking function return errors for every function throughout the entire hierarchy of the code base
  • With exceptioins the advantages are:

  - you can catch an error anywhere in the code base (they "bubble up", or propagate up to a higher level function)

  - you can seperate your normal logic (code) from your error handling.

  - if you don't handle the error at some point, your program will be halted

• • try, throw, catch a std::runtime_error("...")
  • The catch function is only executed if an exception has been thrown
  • Illustration of how exceptions can propagate out of functions
  • You can decide the level at which you want to catch an exception 6:04
  • Catch and rethrow 6:40
  • You can throw anything you want: an object, an Integer, string, pointer, etc.
  • You van overload the catch functions based on the type of information thrown

</code>

• Use catch(...) to catch any uncaught excepions 8:55
• WORK-IN-PROGRESS