Difference between revisions of "Intermediate C++ Game Programming Tutorial 22"
From Chilipedia
(→Video Timestamp Index) |
(→Video Timestamp Index) |
||
| Line 28: | Line 28: | ||
*:- if you don't handle the error at some point, your program will be halted | *:- if you don't handle the error at some point, your program will be halted | ||
</div> | </div> | ||
| − | * <code>try</code>, <code>throw</code>, <code>catch</code> a <code>std::runtime_error("...")</code> | + | * Example code to demonstrate <code>try</code>, <code>throw</code>, <code>catch</code> of a <code>std::runtime_error("...")</code> [https://youtu.be/DMdyz0lrFBI?t=3m53s 3:53] |
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
** The <code>catch</code> function is only executed if an exception has been thrown | ** The <code>catch</code> function is only executed if an exception has been thrown | ||
Revision as of 05:28, 11 November 2019
In this video we learn how to use C++ exceptions to take our error handling to the next level. There is a lot of fear and ignorance surrounding exceptions among "C++ Programmers", and Chili's goal here is to elevate you guys above the shit-tier level to coders who can actually use this feature to its full extent. The second part of this tutorial will give concrete, practical examples of using exceptions in an actual game scenario.
Topics Covered
- Basic exception
tryingthrowing andcatching - Exceptions 'bubbling up'
- Rethrowing with
throw -
std::exceptionand its derivatives - Polymorphism in exception handling
-
catch(...) - Throw by value, catch by
constreference - Exceptions and destructors
-
noexceptand move constuctors vs. standard containers
Video Timestamp Index
- Intro: exceptions are the main way of handling errors in C++ 0:10
- 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
- Comparing error handling with and without exceptions 1:40
- 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
- Example code to demonstrate
try,throw,catchof astd::runtime_error("...")3:53
- The
catchfunction 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
throwanything you want: an object, an Integer, string, pointer, etc. - You van overload the
catchfunctions based on the type of information thrown
- The
- Use
catch(...)to catch any uncaught excepions 8:55 - WORK-IN-PROGRESS
Extra Discussion
I had an interesting exchange with a viewer, and made a bit of a writeup here: essay time.
