Intermediate C++ Game Programming Tutorial 6 - Revision history

Chili: /* Homework */

2020-04-27T12:29:20Z

‎Homework

Chili: /* Video Timestamp Index */

2017-10-13T04:36:15Z

‎Video Timestamp Index

Chili: /* Video Timestamp Index */

2017-10-13T04:35:54Z

‎Video Timestamp Index

Chili at 12:56, 22 September 2017

2017-09-22T12:56:41Z

Chili: /* Errata */

2017-09-22T10:29:53Z

‎Errata

Chili: /* Errata */

2017-09-18T14:23:47Z

‎Errata

Chili: /* Errata */

2017-07-27T14:17:24Z

‎Errata

Chili: /* Errata */

2017-07-15T16:40:13Z

‎Errata

Chili at 16:12, 15 July 2017

2017-07-15T16:12:41Z

Chili at 14:31, 15 July 2017

2017-07-15T14:31:07Z

← Older revision		Revision as of 12:29, 27 April 2020
Line 55:		Line 55:

	The string routines developed during Intermediate are available for use (but are not strictly necessary). The student may not modify any of the test code. The student may not use any additional classes/functions from the standard library or any 3rd party library. If necessary, it is recommended that the Stack class be developed in a separate solution and tested with custom testing code and diagnostic outputs. Then when the Stack class is deemed ready, it can be transplanted into the test solution for final validation.		The string routines developed during Intermediate are available for use (but are not strictly necessary). The student may not modify any of the test code. The student may not use any additional classes/functions from the standard library or any 3rd party library. If necessary, it is recommended that the Stack class be developed in a separate solution and tested with custom testing code and diagnostic outputs. Then when the Stack class is deemed ready, it can be transplanted into the test solution for final validation.
		+
		+	Solution video available here: [https://www.youtube.com/watch?v=lxAzSRxxrH0 homework solution]

	== Errata ==		== Errata ==

@@ Line 17: / Line 17: @@
 == Video Timestamp Index ==
 * [https://youtu.be/OwDJGrV3pgM Video Start]
-* [https://youtu.be/OwDJGrV3pgM?t=2m36s List of Special Member Functions]
+* [https://youtu.be/OwDJGrV3pgM?t=2m36s Announcing Member Functions]
 * [https://youtu.be/OwDJGrV3pgM?t=3m33s Destructors]
 * [https://youtu.be/OwDJGrV3pgM?t=8m26s RAII]

@@ Line 17: / Line 17: @@
 == Video Timestamp Index ==
 * [https://youtu.be/OwDJGrV3pgM Video Start]
-* [https://youtu.be/OwDJGrV3pgM?t=2m36s Announcing Member Functions]
+* [https://youtu.be/OwDJGrV3pgM?t=2m36s List of Special Member Functions]
 * [https://youtu.be/OwDJGrV3pgM?t=3m33s Destructors]
 * [https://youtu.be/OwDJGrV3pgM?t=8m26s RAII]

@@ Line 57: / Line 57: @@
 == Errata ==
-* '''It is very important''' to check for '''self assignment'''. If the user of your class tries to do <code>myObj = myObj;</code>, and you do not detect this case, what your code will do is allocate new memory, set myObj's internal pointer to that memory (leaking it), and then it will delete the new memory, giving you an invalid pointer. Actual cancer. Chili neglected to do a check for this case in his examples or in the homework solution, and for this he is surely going to Hell.
+* <span style="color:red">'''It is very important'''</span> to check for '''self assignment'''. If the user of your class tries to do <code>myObj = myObj;</code>, and you do not detect this case, what your code will do is allocate new memory, set myObj's internal pointer to that memory (leaking it), and then it will delete the new memory, giving you an invalid pointer. Actual cancer. Chili neglected to do a check for this case in his examples or in the homework solution, and for this he is surely going to Hell.
 * The destructor of <code>DynamicIntArray</code> frees the dynamic memory block with <code>delete pArray</code>, but since it was allocated with <code>new int[]</code> it should have been freed with <code>delete [] pArray</code>.
 * The text at 39:38 got messed up and goes off of the screen partially. It should have read: "Remember, before assignment the object being assigned to already owned some memory, and when we overwrite the pointer we lose track of that memory forever."

@@ Line 57: / Line 57: @@
 == Errata ==
-'''It is very important''' to check for '''self assignment'''. If the user of your class tries to do <code>myObj = myObj;</code>, and you do not detect this case, what your code will do is allocate new memory, set myObj's internal pointer to that memory (leaking it), and then it will delete the new memory, giving you an invalid pointer. Actual cancer. Chili neglected to do a check for this case in his examples or in the homework solution, and for this he is surely going to Hell.
+* '''It is very important''' to check for '''self assignment'''. If the user of your class tries to do <code>myObj = myObj;</code>, and you do not detect this case, what your code will do is allocate new memory, set myObj's internal pointer to that memory (leaking it), and then it will delete the new memory, giving you an invalid pointer. Actual cancer. Chili neglected to do a check for this case in his examples or in the homework solution, and for this he is surely going to Hell.
+* The destructor of <code>DynamicIntArray</code> frees the dynamic memory block with <code>delete pArray</code>, but since it was allocated with <code>new int[]</code> it should have been freed with <code>delete [] pArray</code>.
-The destructor of <code>DynamicIntArray</code> frees the dynamic memory block with <code>delete pArray</code>, but since it was allocated with <code>new int[]</code> it should have been freed with <code>delete [] pArray</code>.
+* The text at 39:38 got messed up and goes off of the screen partially. It should have read: "Remember, before assignment the object being assigned to already owned some memory, and when we overwrite the pointer we lose track of that memory forever."
+* In <code>Stack::Element</code>, we implement the destructor and the copy constructor, but not the copy assignment. This violates the Rule of 3, and if someone later accidentally uses the copy assignment operator (fairly possible), they're gonna get their shit fucked up. Since we don't need it, it would be best just to delete it with <code>= delete</code>.
 The text at 39:38 got messed up and goes off of the screen partially. It should have read: "Remember, before assignment the object being assigned to already owned some memory, and when we overwrite the pointer we lose track of that memory forever."
-−
 In <code>Stack::Element</code>, we implement the destructor and the copy constructor, but not the copy assignment. This violates the Rule of 3, and if someone later accidentally uses the copy assignment operator (fairly possible), they're gonna get their shit fucked up. Since we don't need it, it would be best just to delete it with <code>= delete</code>.
 == See also ==
 * [[Intermediate C++ Game Programming Tutorial 7|Next in series (Tutorial 7)]]
 * [[Intermediate C++ Game Programming Series]]

← Older revision		Revision as of 14:23, 18 September 2017
Line 57:		Line 57:

	== Errata ==		== Errata ==
		+	'''It is very important''' to check for '''self assignment'''. If the user of your class tries to do <code>myObj = myObj;</code>, and you do not detect this case, what your code will do is allocate new memory, set myObj's internal pointer to that memory (leaking it), and then it will delete the new memory, giving you an invalid pointer. Actual cancer. Chili neglected to do a check for this case in his examples or in the homework solution, and for this he is surely going to Hell.
		+
	The destructor of <code>DynamicIntArray</code> frees the dynamic memory block with <code>delete pArray</code>, but since it was allocated with <code>new int[]</code> it should have been freed with <code>delete [] pArray</code>.		The destructor of <code>DynamicIntArray</code> frees the dynamic memory block with <code>delete pArray</code>, but since it was allocated with <code>new int[]</code> it should have been freed with <code>delete [] pArray</code>.

@@ Line 13: / Line 13: @@
 * Deleting Special Member Functions with <code>= delete</code>
 * Conditions when Special Members Cannot be Generated by Compiler
@@ Line 57: / Line 55: @@
 The string routines developed during Intermediate are available for use (but are not strictly necessary). The student may not modify any of the test code. The student may not use any additional classes/functions from the standard library or any 3rd party library. If necessary, it is recommended that the Stack class be developed in a separate solution and tested with custom testing code and diagnostic outputs. Then when the Stack class is deemed ready, it can be transplanted into the test solution for final validation.
 == See also ==
 * [[Intermediate C++ Game Programming Tutorial 7|Next in series (Tutorial 7)]]
 * [[Intermediate C++ Game Programming Series]]

← Older revision		Revision as of 14:31, 15 July 2017
Line 1:		Line 1:
−	This tutorial is epoch-making, DO NOT SKIP IT. The ostensive main topic for this video is destructors, but that is not where its soul lies. After learning about dtors, we are ready to discuss a matter that is at the heart of C++: RAII. This will form the bridge between low-level memory management, and high level smart objects. We also discuss the important concept of deep copying and the Rule of 3, and related to this, we review the 4 original special member functions. AND there are discussion of a bunch of other random bullshit, like converting construction for example. It's a big video is what I'm tryin' to say here.	+	This tutorial is epoch-making; <span style="color:red">'''DO NOT SKIP IT'''</span>. The ostensive main topic for this video is destructors, but that is not where its soul lies. After learning about dtors, we are ready to discuss a matter that is at the heart of C++: RAII. This will form the bridge between low-level memory management, and high level smart objects. We also discuss the important concept of deep copying and the Rule of 3, and related to this, we review the 4 original special member functions. AND there are discussion of a bunch of other random bullshit, like converting construction for example. It's a big video is what I'm tryin' to say here.

	== Topics Covered ==		== Topics Covered ==