Intermediate C++ Game Programming Tutorial 3 - Revision history

Chili: /* IMPORTANT NOTE */

2019-02-02T17:01:15Z

‎IMPORTANT NOTE

Chili: /* IMPORTANT NOTE */

2019-02-02T16:59:45Z

‎IMPORTANT NOTE

Chili: /* IMPORTANT NOTE */

2018-06-23T17:21:09Z

‎IMPORTANT NOTE

Chili at 17:19, 23 June 2018

2018-06-23T17:19:17Z

Chili at 14:34, 5 June 2017

2017-06-05T14:34:51Z

Chili: /* Homework */

2017-06-01T13:41:38Z

‎Homework

Chili: /* Notes */

2017-05-30T01:50:43Z

‎Notes

Chili: /* Bonus Assignment */

2017-05-30T01:47:44Z

‎Bonus Assignment

Chili: /* Bonus Assignment */

2017-05-30T01:42:57Z

‎Bonus Assignment

Chili: /* Homework */

2017-05-30T01:41:35Z

‎Homework

@@ Line 4: / Line 4: @@
 In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it. Long story short it jams null characters between every real character you read (but only in Debug configuration).
-As a workaround you can do some bullshit where you ignore every other character or something like that. Or you can use Visual Studio 2015; it works fine. It also works fine when you build in Release configuration. Hopefully these fuckers fix this.
+As a workaround you can do some bullshit where you ignore every other character or something like that. Or you can use Visual Studio 2015; it works fine. It also seems to work fine when you build in Release configuration. Hopefully these fuckers fix this.
 For more details:

@@ Line 2: / Line 2: @@
 == <span style="color:red">IMPORTANT NOTE</span> ==
-In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it. Long story short it jams null characters between every real character you read.
+In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it. Long story short it jams null characters between every real character you read (but only in Debug configuration).
-As a workaround you can do some bullshit where you ignore every other character or something like that. Or you can use Visual Studio 2015; it works fine. Hopefully these fuckers fix this.
+As a workaround you can do some bullshit where you ignore every other character or something like that. Or you can use Visual Studio 2015; it works fine. It also works fine when you build in Release configuration. Hopefully these fuckers fix this.
 For more details:

@@ Line 2: / Line 2: @@
 == <span style="color:red">IMPORTANT NOTE</span> ==
-In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it.
+In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it. Long story short it jams null characters between every real character you read.
 For more details:
-* [https://developercommunity.visualstudio.com/content/problem/252047/something-wrong-with-getch-in-loops.html Visual Studio Developer Community]
+* [https://developercommunity.visualstudio.com/content/problem/252047/something-wrong-with-getch-in-loops.html Visual Studio Developer Community (upvote this)]
-* [http://forum.planetchili.net/viewtopic.php?f=3&t=4404 forum topic]
+* [http://forum.planetchili.net/viewtopic.php?f=3&t=4404 Forum Topic]
 == Topics Covered ==

← Older revision		Revision as of 17:19, 23 June 2018
Line 1:		Line 1:
	In this tutorial we start from the barest bone starting point. Using only two simple functions: <code>_putch()</code> to output a character onto the console and <code>_getch()</code> to read a key from the keyboard, we build up a concept and theory of string storage, basic text input and output, and parsing operations. It might seem like reinventing the wheel, but you know what they say. The squeaky wheel <code>gets()</code> the cheese. Seriously though, this shit is gonna give us a solid foundation of low-level understanding on which we can later build up a fortress of high-level C++ awesomeness.		In this tutorial we start from the barest bone starting point. Using only two simple functions: <code>_putch()</code> to output a character onto the console and <code>_getch()</code> to read a key from the keyboard, we build up a concept and theory of string storage, basic text input and output, and parsing operations. It might seem like reinventing the wheel, but you know what they say. The squeaky wheel <code>gets()</code> the cheese. Seriously though, this shit is gonna give us a solid foundation of low-level understanding on which we can later build up a fortress of high-level C++ awesomeness.
		+
		+	== <span style="color:red">IMPORTANT NOTE</span> ==
		+	In a recent update to Visual Studio 2017 Microsoft has (in their infinite wisdom) introduced a fucking annoying-ass bug (or maybe bugs) into the conio library. It basically fucks with the console input bullshit that we develop in this tutorial and I hate it.
		+
		+	For more details:
		+	* [https://developercommunity.visualstudio.com/content/problem/252047/something-wrong-with-getch-in-loops.html Visual Studio Developer Community]
		+	* [http://forum.planetchili.net/viewtopic.php?f=3&t=4404 forum topic]

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

@@ Line 43: / Line 43: @@
 </syntaxhighlight>
 </div>
 == See also ==
 * [[Intermediate C++ Game Programming Tutorial 4|Next in series (Tutorial 4)]]
 * [[Intermediate C++ Game Programming Series]]

@@ Line 21: / Line 21: @@
 == Homework ==
 Prompt the user to input a positive integer, find that number in the Fibonacci sequence, and then output it to the console. For example, if the user enters the number 9, you should output the 9th Fibonacci number (34) to the console.  There's only one catch: you're not allowed to use any library functions except for <code>_putch()</code>, <code>_getch()</code>, and <code>_kbhit()</code>. You can use the functions that we have already developed in this video.
 === Bonus Assignment ===

@@ Line 15: / Line 15: @@
 == Notes ==
-This stuff that we're doing here with the strings, don't get the wrong idea. This is not the way forward. We're doing this stuff right now because it makes sense to learn about low-level string bullshit at this point and it gives us a chance to practice out newly-acquired pointer skills. However, using c-strings widely in your code is a terrible idea. They are inconvenient and extremely error-prone. Not sexy at all
+This stuff that we're doing here with the strings, don't get the wrong idea. This is not the way forward. We're doing this stuff right now because it makes sense to learn about low-level string bullshit at this point and it gives us a chance to practice out newly-acquired pointer skills. However, using c-strings widely in your code is a terrible idea. They are inconvenient and extremely error-prone. Not sexy at all.
-One we get our practice in with basic pointer ops, strings, file I/O, and memory management, we will be ditching that caveman shit and upgrading to C++ sexy shits. That means we will be ditching c-strings for <code>std::string</code> sometime in the nearish future. But that doesn't mean you can skip this stuff. If you wanna be top tier programmer, you should have this background info. And sometimes (like when you're interfacing with libraries/APIs for example) you still need to use c-strings, even if only a little.
+Once we get our practice in with basic pointer ops, strings, file I/O, and memory management, we will be ditching that caveman shit and upgrading to C++ sexy shits. That means we will be ditching c-strings for <code>std::string</code> ''sometime in the nearish future''. But that doesn't mean you can skip this stuff. If you wanna be top tier programmer, you should have this background knowledge as well. And sometimes (like when you're interfacing with libraries/APIs for example) you still need to use c-strings, even if only a little.
 == Homework ==

@@ Line 23: / Line 23: @@
 === Bonus Assignment ===
-The string-to-integer parsing algorithm shown in the video was written to mimic the concept of positional notation as close as possible (i.e. the value of '689' is 6 x 100 + 8 x 10 + 9 x 1). However, this naive implementation has room for improvement. Specifically, a small adjustment can enable us to convert the number without first scanning right to the one's digit. If you want a bonus challenge, try to make this optimization on your own. Expand the section below for a possible solution.
+The string-to-integer parsing algorithm shown in the video was written to mimic the concept of positional notation as closely as possible (i.e. the value of '689' is 6 x 100 + 8 x 10 + 9 x 1). However, this naive implementation has room for improvement. Specifically, a small adjustment can enable us to convert the number without first scanning right to the one's digit. If you want a bonus challenge, try to make this optimization on your own. Expand the section below for a possible solution.
 <div class="mw-collapsed mw-collapsible" style="width:450px">

@@ Line 32: / Line 32: @@
 	for( ; *s >= '0' && *s <= '9'; s++ )
+	{
-		// shift entire sum over by one decimal place
+		// shift entire sum left by one decimal place
 		sum *= 10;
 		// add in new lowest digit