Difference between revisions of "Intermediate C++ Game Programming Tutorial 7"
(Created page with "We finally ditch our janky makeshift chili:: routines and use some real shit here. Standard streams (std::cin / std::cout / std::fstream) are covered, and then we talk about s...") |
|||
| Line 1: | Line 1: | ||
| − | We finally ditch our janky makeshift chili:: routines and use some real shit here. Standard streams (std::cin / std::cout / std::fstream) are covered, and then we talk about string manipulation with std::string. | + | We finally ditch our janky makeshift <code>chili::</code> routines and use some real shit here. Standard streams (<code>std::cin</code> / <code>std::cout</code> / <code>std::fstream</code>) are covered, and then we talk about string manipulation with <code>std::string</code>. We'll also cover some other less well-known dank C++ code memes, so check it out. Note that this video is more of an overview / whirlwind tour; it introduces various techniques and gives examples, but don't expect a detailed or exhaustive treatment here. |
== Topics Covered == | == Topics Covered == | ||
| − | * | + | * C++ Steams |
| − | * | + | * std::cin / std::cout |
| − | * | + | * Insertion / extraction operators |
| − | + | * <code>std::endl</code> and buffered I/O flushing | |
| − | + | * <code><iomanip></code> | |
| − | + | * Cleaning out an input stream | |
| − | * <code> | + | * <code>std::numeric_limits<></code> |
| − | * | + | * <code>std::string</code> |
| − | * | + | * <code>OutputDebugString</code> |
| − | * | + | * <code>std::stringstream</code> |
| − | * | + | |
== Video Timestamp Index == | == Video Timestamp Index == | ||
| − | * [https://youtu.be/ | + | * [https://youtu.be/OwDJGrV] |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Source Code == | == Source Code == | ||
| − | [https://github.com/planetchili/ | + | [https://github.com/planetchili/Snek GitHub Repo for Snek]<br /> |
| − | + | ||
| − | + | ||
== Homework == | == Homework == | ||
Revision as of 22:02, 27 July 2017
We finally ditch our janky makeshift chili:: routines and use some real shit here. Standard streams (std::cin / std::cout / std::fstream) are covered, and then we talk about string manipulation with std::string. We'll also cover some other less well-known dank C++ code memes, so check it out. Note that this video is more of an overview / whirlwind tour; it introduces various techniques and gives examples, but don't expect a detailed or exhaustive treatment here.
Topics Covered
- C++ Steams
- std::cin / std::cout
- Insertion / extraction operators
-
std::endland buffered I/O flushing -
<iomanip> - Cleaning out an input stream
-
std::numeric_limits<> -
std::string -
OutputDebugString -
std::stringstream
Video Timestamp Index
Source Code
Homework
The homework is to create a stack container that is implemented with with a linked list data structure. The skeleton of the interface for the Stack class is given in the source code (see the Downloads above). These are the minimum functions that must be implemented. For further information on stacks, see this video. For further information on linked lists, see this video. Furthermore, additional research is highly recommended.
The behaviors of the interface functions are for the student to infer, with the exception of the Pop() function. In the case of calling Pop() on an empty stack, the function shall return -1. The internal implementation details are also to be determined by the student, but they must at their core use a linked list data structure.
When the Stack is fully implemented and the program is executed, there are 8 test routines that will be run. All test routines should output 'Passed' to the console for the homework to be considered solved. Furthermore, the heap memory will be monitored at the end of the program and any dynamic memory that has not been freed will trigger a diagnostic error message. It is required that no diagnostic error be output for the homework to be considered solved.
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.
Errata
The destructor of DynamicIntArray frees the dynamic memory block with delete pArray, but since it was allocated with new int[] it should have been freed with delete [] pArray.
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."
