In the previous lesson (), we discussed which attributes of a function are used to differentiate overloaded functions from each other. If an overloaded function is not properly differentiated from the other overloads of the same name, then the compiler will issue a compile error. However, having a set of …
In the prior lesson (), we introduced the concept of function overloading, which allows us to create multiple functions with the same name, so long as each identically named function has different parameter types (or the functions can be otherwise differentiated). In this lesson, we’ll take a closer look at …
Consider the following program: int add(int x, int y) { return x + y; } When this function is compiled, the compiler will determine that x + y evaluates to an int, then ensure that type of the return value matches the declared return type of the function (or that …
In lesson , we discussed how expressions are evaluated according to the precedence and associativity of their operators. Consider the following expression: int x { 2 + 3 }; When binary operator+ is invoked, it is given two operands, both of type int. Because both operands are of the same …
In the previous lesson (), we covered numeric promotions, which are conversions of specific narrower numeric types to wider numeric types (typically int or double) that can be processed efficiently. C++ supports another category of numeric type conversions, called . These numeric conversions cover additional type conversions between fundamental types. …
In lesson , we noted that C++ has minimum size guarantees for each of the fundamental types. However, the actual size of these types can vary based on the compiler and architecture. This variability was allowed so that the int and double data types could be set to the size …
In lesson , we covered syntax errors, which occur when you write code that is not valid according to the grammar of the C++ language. The compiler will notify you of such errors, so they are trivial to catch, and usually straightforward to fix. We also covered semantic errors, which …
In the previous lesson , we discussed how to write and preserve simple tests. In this lesson, we’ll talk about what kind of tests are useful to write to ensure your code is correct. The term is used to describe how much of the source code of a program is …
The last category of flow control statement we’ll cover in this chapter is the halt. A is a flow control statement that terminates the program. In C++, halts are implemented as functions (rather than keywords), so our halt statements will be function calls. Let’s take a brief detour, and recap …
This lesson continues our exploration of switch statements that we started in the prior lesson . In the prior lesson, we mentioned that each set of statements underneath a label should end in a break statement or a return statement. In this lesson, we’ll explore why, and talk about some …
