Intermediate C++ Game Programming Tutorial 17 - Revision history

R vdw: /* Video Timestamp Index */

2019-10-13T13:46:23Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-13T13:45:03Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:34:42Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:28:10Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:27:07Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:25:48Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:16:59Z

‎Video Timestamp Index

R vdw: /* Video Timestamp Index */

2019-10-08T21:14:55Z

‎Video Timestamp Index

R vdw: /* Part 2 Class Specification */

2019-10-08T21:03:58Z

‎Part 2 Class Specification

R vdw: /* Video Timestamp Index */

2019-10-08T20:56:31Z

‎Video Timestamp Index

@@ Line 54: / Line 54: @@
 [https://youtu.be/21uaUOeOof8 Tutorial 17.2]
 * Revisiting the "is-a" principle of Inheritance. Applying it to build a class hierarchy [https://youtu.be/21uaUOeOof8?t=51 0:51]
 * Abstract vs. Concrete classes [https://youtu.be/21uaUOeOof8?t=3m20s 3:20]
 ** Abstract (parent) classes are not supposed to be instantiated (constructors are protected)
 ** Concrete (child) classes are supposed to be instantiated
 * Application of abtract classes on multiple levels [https://youtu.be/21uaUOeOof8?t=4m09s 4:09]
 * Building the Meme Fighter class hierarchy (Abstract class) [https://youtu.be/21uaUOeOof8?t=5m28s 5:28]
 ** Introducing the modifier <code>mutable</code> (an access specifier for data members) [https://youtu.be/21uaUOeOof8?t=10m06s 10:06]
 ** When writing a <code>const</code> member function (i.e. a member function that does not change data members in the class), a <code>mutable</code> data member may be changed in that function
 * Building the Meme Fighter class hierarchy (Concrete classes) [https://youtu.be/21uaUOeOof8?t=13m03s 13:03]
 * Giving the implemented code a test run [https://youtu.be/21uaUOeOof8?t=16m49s 16:49]
@@ Line 67: / Line 72: @@
 * Getting a class diagram in Visual Studio [https://youtu.be/21uaUOeOof8?t=19m26s 19:26]
 * Closing two points of advice [https://youtu.be/21uaUOeOof8?t=19m55s 19:55]
 ** Never break the "is-a" rule
 ** Don't go crazy with applying inheritance
 == Part 2 Class Specification ==

@@ Line 16: / Line 16: @@
 == Video Timestamp Index ==
 [https://youtu.be/O2-jdGGCFkE Tutorial 17.1]
 * What is inheritance? Introducing a simple example <code>class ChildClass : public ParentClass {...};</code>[https://youtu.be/O2-jdGGCFkE?t=15 0:15]
 * Different language used for the same concept [https://youtu.be/O2-jdGGCFkE?t=1m45s 1:45]:
 ** to "inherit" a class, from "parent" to "child",
 ** to "extend" a class, from "base" to "extended",
 ** to "derive" a class, from "base" to "derived",
 ** to "sub-class" a class, from "superclass" to "subclass" (used in Java)
 * Why is inheritance important? no clutter, no repetition of code, no tampering inside deployed classes [https://youtu.be/O2-jdGGCFkE?t=2m44s 2:44]
 * Fictitious but instructive <code>Smasher</code> and <code>EliteSmasher</code> class example [https://youtu.be/O2-jdGGCFkE?t=5m08s 5:08]
 * Inheritance creates an "Is-a relationship" [https://youtu.be/O2-jdGGCFkE?t=8m15s 8:15]
 ** A child class "is-a [kind of]" parent class, so you can pass a child object to functions that expect a reference to a parent object
 ** The ability to refer to a child type with a parent reference (or pointer), allows us to create functions that can work over many types, as long as they all inherit from a common parent
 * Inheritance and constructors: you can't inherit (default) constructors [https://youtu.be/O2-jdGGCFkE?t=9m49s 9:49]
 ** The base class of a class behaves like the first data member of the extended class: it is initialized (constructed) first
 ** The default constructor of a child class has to call a constructor of the parent class
 * Overriding parent functions in the child class [https://youtu.be/O2-jdGGCFkE?t=13m22s 13:22]
 ** In addition to extending functionality of a parent class in a child class, overriding allows you to alter functionality, if you have to
 ** You can invoke the parent version of an overridden function by prefixing the parent class name <code>ParentClass::OverriddenParentFunction();</code>
 ** The private members of the parent class are not accessible to the child class
 * Introducting the <code>protected:</code> access specifier in classes [https://youtu.be/O2-jdGGCFkE?t=16m34s 16:34]
 ** Form of access control that enables children to access members (while keeping members private to all other scopes)
 ** Allows you to apply proper encapsulation of the parent class by setting a separate protected interface only for its children
 ** ROI "Return on invested time" should guide your choice to either i) protect your members, ii) keep your members private but build a proteced interface
 * Recap of key techniques learned about inheritance [https://youtu.be/O2-jdGGCFkE?t=21m05s 21:05]
 * Cool it down with applying inheritance, risk of mis/overusage of the concept [https://youtu.be/O2-jdGGCFkE?t=22m08s 22:08]
 [https://youtu.be/21uaUOeOof8 Tutorial 17.2]

@@ Line 42: / Line 42: @@
 [https://youtu.be/21uaUOeOof8 Tutorial 17.2]
-* Revisiting the "is-a" principle and apply to the design of a class hierarchy using inheritance [https://youtu.be/21uaUOeOof8?t=51 0:51]
+* Revisiting the "is-a" principle of Inheritance. Applying it to build a class hierarchy [https://youtu.be/21uaUOeOof8?t=51 0:51]
 * Abstract vs. Concrete classes [https://youtu.be/21uaUOeOof8?t=3m20s 3:20]
 ** Abstract (parent) classes are not supposed to be instantiated (constructors are protected)

@@ Line 56: / Line 56: @@
 * Closing two points of advice [https://youtu.be/21uaUOeOof8?t=19m55s 19:55]
 ** Never break the "is-a" rule
-**
+** Don't go crazy with applying inheritance
 == Part 2 Class Specification ==

@@ Line 54: / Line 54: @@
 * Recap of topics covered [https://youtu.be/21uaUOeOof8?t=18m40s 18:40]
 * Getting a class diagram in Visual Studio [https://youtu.be/21uaUOeOof8?t=19m26s 19:26]
 == Part 2 Class Specification ==

@@ Line 71: / Line 71: @@
 <code>MemeStoner</code>:
 * Has 80 hp, 4 speed, and 10 power
-* Has a <code>SpecialMove</code> function that takes no parameters and has a 1/2 chance of adding 3 speed, increasing power by 69/42, adding 10 hp, and adding to the entity's name
+* Has a <code>SpecialMove</code> function that takes no parameters and has a 1/2 chance of adding 3 speed, increasing power by 69/42, adding 10 hp, and adding "Super" to the entity's name
 == Source Code ==