Intermediate C++ Game Programming Tutorial 22 - Revision history

R vdw: /* Video Timestamp Index */

2019-11-24T20:59:07Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:56:14Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:50:22Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:49:23Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:47:01Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:42:49Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:40:25Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:38:37Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:37:12Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-11-24T20:34:05Z

‎Video Timestamp Index

@@ Line 88: / Line 88: @@
 * Exceptions, applied in practice [[RPG Project Twin]] in the Chili Framework [https://youtu.be/_6G5yDgoWiA?t=0m10s 0:10]
 <div class="mw-collapsible-content">
-** A custom class <code>ChiliException</code> was defined (not recommended) that holds message, filename and line number information and virtual functions for information getters defined in derived classes
+** A custom class <code>ChiliException</code> is defined (not recommended, rather inherit from <code>std::exception</code>) that holds message, filename and line number information and virtual functions for information getters defined in derived classes
-** An inner class <code>Graphics::Exception</code> was defined that inherits from <code>ChiliException</code> and adds a data member of type <code>HRESULT></code> (used in DirectX)
+** An inner class <code>Graphics::Exception</code> is defined that inherits from <code>ChiliException</code> and adds a data member of type <code>HRESULT></code> (used in DirectX)
 ** The Windows API doesn't use exceptions, so individual tests for every function using <code>FAILED</code> calls are used to throw exceptions. Macros such as <code>CHILI_GFX_EXCEPTION()</code> are used to generate the exceptions
 ** In <code>Main.cpp</code>, Chili uses a <code>try{ }</code> inside another <code>try{ }</code>. The first is used to test if the creation of a <code>MainWindow</code> object succeeds, the second to throw exceptions using <code>wnd.ShowMessageBox()</code> of that <code>MainWindow</code> class

@@ Line 85: / Line 85: @@
 </div>
 [https://youtu.be/_6G5yDgoWiA Tutorial 22 Part 2]
 * Exceptions, applied in practice [[RPG Project Twin]] in the Chili Framework [https://youtu.be/_6G5yDgoWiA?t=0m10s 0:10]
 ** A custom class <code>ChiliException</code> was defined (not recommended) that holds message, filename and line number information and virtual functions for information getters defined in derived classes
 ** An inner class <code>Graphics::Exception</code> was defined that inherits from <code>ChiliException</code> and adds a data member of type <code>HRESULT></code> (used in DirectX)
 ** The Windows API doesn't use exceptions, so individual tests for every function using <code>FAILED</code> calls are used to throw exceptions. Macros such as <code>CHILI_GFX_EXCEPTION()</code> are used to generate the exceptions
 ** In <code>Main.cpp</code>, Chili uses a <code>try{ }</code> inside another <code>try{ }</code>. The first is used to test if the creation of a <code>MainWindow</code> object succeeds, the second to throw exceptions using <code>wnd.ShowMessageBox()</code> of that <code>MainWindow</code> class
 * The use of macros to generate exceptions [https://youtu.be/_6G5yDgoWiA?t=4m22s 4:22]
 ** A macro <code>CHILI_GFX_EXCEPTION()</code> is implemented that expands to a constructor for <code>Graphics::Exception()</code>, that also takes two pre-processor defined macros (defined by the compiler):
 *:- <code>_CRT_WIDE(__FILE__)</code>, for the filename
 *:- <code>__LINE__</code>, for the line number in the code
 ** You need to use a macro for this to get the line number of each function call at the different throw points (instead of the line number of the function definition)
 * The use of the <code>HRESULT</code> function  [https://youtu.be/_6G5yDgoWiA?t=5m42s 5:42]
 ** <code>>HRESULT hr</code> is used to perform a lookup  <code>DXGetErrosString(hr)</code> of the error name string
 * Working with streams (<code>std::ifstream file</code> and exceptions in the <code>Sound</code> class [https://youtu.be/_6G5yDgoWiA?t=7m05s 7:05]
 ** For example: file reading to load sounds
 ** Steams don't work with exceptions by default, you have to check the error flags to throw based on that
 ** <code>file.exceptions(std::ifstream::failbit | std::ifstream::badbit);</code> turns on the excceptions for the failure and bad flags
 * Recovering from an exception [https://youtu.be/_6G5yDgoWiA?t=9m33s 9:33]
 ** For example: loading resources (like sound). By using a <code>soft_fail</code> flag, an empty sound gets added to the matrix of sounds so that the program can continue. In case of a hard fail the exception gets rethrown and stops the program.
 ** Chili uses <code>#ifndef NDEBUG throw e; #endif</code> to always throw when in debug mode
 * Recap of main take-aways [https://youtu.be/_6G5yDgoWiA?t=11m32s 11:32]
 ** DO inherit from <code>std::exception</code>
 ** DO use exceptions for errors that happan that are out of programmer's control
@@ Line 116: / Line 128: @@
 ** DO not mark functions <code>noexcept</code> just because they happen not to throw right now - they might in the future so think carefully before going down the noexcept path
 ** DO NOT use exceptions for flow control
 * Homework assignment [https://youtu.be/_6G5yDgoWiA?t=14m06s 14:06]
 == Extra Discussion ==

@@ Line 116: / Line 116: @@
 ** DO not mark functions <code>noexcept</code> just because they happen not to throw right now - they might in the future so think carefully before going down the noexcept path
 ** DO NOT use exceptions for flow control
 == Extra Discussion ==

@@ Line 115: / Line 115: @@
 ** DO mark functions as <code>noexcept</code> if you are confident that they will NEVER want to throw an exception, either now, or later on in development
 ** DO not mark functions <code>noexcept</code> just because they happen not to throw right now - they might in the future so think carefully before going down the noexcept path
 == Extra Discussion ==

@@ Line 104: / Line 104: @@
 ** For example: loading resources (like sound). By using a <code>soft_fail</code> flag, an empty sound gets added to the matrix of sounds so that the program can continue. In case of a hard fail the exception gets rethrown and stops the program.
 ** Chili uses <code>#ifndef NDEBUG throw e; #endif</code> to always throw when in debug mode
-** Recap of main take-aways [https://youtu.be/_6G5yDgoWiA?t=11m32s 11:32]
+* Recap of main take-aways [https://youtu.be/_6G5yDgoWiA?t=11m32s 11:32]
 == Extra Discussion ==