Home Previous Next

CSC100 :: Lecture Note :: Week 10
Assignments | Code | Handouts | Resources | Email Thurman {Twitter::@compufoo Facebook::CSzero}
{GDT::Bits:: Time  |  Weather  |  Populations  |  Special Dates}

Overview
Assignment(s):
Code: [switch statement] Switch.cpp
[functions] global.cpp | noglobal.cpp | scope.cpp | i2fi.cpp | refparams.cpp
[arrays] arrays0.cpp | arrays1.cpp | random.cpp | arrays2.cpp | BingoCard.cpp | bingo.cpp

### The `switch` Statement

The `switch` statement is a multi-way decision that tests whether an integral-EXPR matches one of a number of constant integral values, and branches accordingly.

```   switch (integral-EXPR) {
case const-expr: statements
case const-expr: statements
default: statements          /*optional*/
}
```

The body of a `switch` almost always contains a compound statement. The compound statement usually contains one or more `case` labels. Optionally, the body of `switch` can contain a `default` label. Both `case` and `default` are keywords of the language.

A good time to use a `switch` statement is when you encounter nested `if` statements that are checking to see of a specific integral value is equal to a set of constant integral values.

```   const int ADULT_AGE = 21;
const int FIRST_MILESTONE_AGE = 30;
const int SECOND_MILESTONE_AGE = 40;
const int THIRD_MILESTONE_AGE = 50;
const int RETIREMENT_AGE = 65;
const int CENTURY_MARK = 100;

/* here are some nested if statements */
if (age == 21)
statement;
else
if (age == 30 || age == 40 || age == 50)
statement;
else
if (age == 65)
statement;
else
if (age == 100)
statement;

/* the nested if's rewritten using a switch statement */
switch (age) {
case 21:
statement;
break;  // what would happen if this statement is rm'd?
case 30:
case 40:
case 50:
statement;
break;
case (65):  // note: () usage around the case EXPR is allowed
statement;
break;
case (100):
statement;
break;  // good form to have this break statement
}
```

Some benefits gained from using the `switch` statement versus the nested `if` statements.

• easier to modify/restructure

Points that require understanding.

• The `switch` EXPR may be any EXPR that evaluates to an integral value (this includes `long` and `unsigned long`).
• All `case` constant EXPRs must be unique.
• The `case` and `default` labels can occur in any order.
• Each `case` serves as a label and program execution falls through to the next `case` unless explicitly told to do otherwise.
• The `break` statement causes immediate exit from a `switch`
• `break` and `return` are the most common ways to exit a  `switch`.
• Use caution when falling through cases. Good form is to put a `break` after the last `case`.

More examples using the `switch` statement.

```   switch (nbr) {
case 1: cout << "one"; break;
case 2: cout << "two"; break;
case 3: cout << "three"; break;
case 4: cout << "four"; break;
case 5: cout << "five"; break;
default: cout << "enough of this..."; break;
}

float f = 3.14f;
switch (f) { ... }  is illegal -- the switch EXPR is not integral

float pi = 3.14f;
switch (nbr) {
case nbr % 2: ...   is illegal -- case EXPR is not constant
case pi: ...  is illegal -- case EXPR is not constant, nor is
...                         it an integral value
}

switch (nbr) {
case 1:
case 1: ...  is illegal -- case EXPR is not unique
...
}
```

GDT::C++::Code:: Switch.cpp

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Introduction to Functions

Lowest level ideas become EXPRs, EXPRs are grouped into statements, and statements are grouped together into blocks and functions.

A function is a set of statements that have been collected together and given a name.

Functions break large computing tasks into smaller ones, and enable people to build on what others have done instead of starting over from scratch. Functions support reuse.

Functions hide details of operation from parts of the program that don't need to know about them. Functions support information hiding.

Functions usually consist of zero or more statements, and a collection of local data. Functions support encapsulation.

Programs generally consist of many small functions rather than a few big ones. Functions support modularity.

Repetitive statements should be grouped into a function. Functions eliminate duplicate code.

Additional benefits derived from using functions.

• improves a program's overall readability by reducing the conceptual complexity of the program
• programs can be implemented in less time (generally, finding and figuring out how to call a function takes less time than having to write the function)
• makes testing easier
• improves the overall quality of the program (functions are usually well tested and efficiently implemented)
• allows programs to be implemented in "parts"
• supports problem solving techniques such as "divide-and-conquer" and "step-wise refinement"

Functions that perform generic tasks can be added to a library. Library functions can be used in multiple programs. The C and C++ languages come with extensive libraries that contain numerous functions.

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Function Terminology

The act of executing a set of statements associated with a function is known as calling the function. If function A calls function B, then function A is referred to as the calling or caller function and function B is the called function.

Arguments are a list of EXPRs that are evaluated and whose values are passed to the function. (Note: C and C++ are " pass-by-value" languages.) A function does not need to take arguments. If function A calls function B, then arguments allows function A to communicate information to function B.

Arguments, if any, that are passed to a function B, are parameters within function B. Parameters are treated as initialized local (i.e. `auto` variables).

When a function is done, it returns to the caller by executing a `return` statement.

Functions can "return a value" back to the caller; thus, if function A calls function B, then the return value allows function B to communicate with function A.

Before a function can be called, it must be declared. A function declaration that also includes the type(s) of the parameters is called a prototype.

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Function Prototypes

A function must be declared (i.e. prototyped) before it is used.

Syntax.

```   return-type function-name(parameter types, if any);
```

Examples.

```   int maxValue(int, int);
//returns an int; receives two int values as parameters

float getSalary(void);
//returns a float; doesn't take any parameters

double computeFactorial(int number);
//returns a double; receives an int value
//parameter types can have a tag specified with them, but the
//    tag is ignored by the compiler; tags are used for
//    documentation purposes only and can help the readability of
//    a program; they have what is referred to as function
//    prototype scope

char getGrade(short, unsigned char, unsigned char);
//returns a character; receives a short value and two
//    unsigned characters as parameters

void abort(void);
```

Function prototypes are used by the compiler to help make sure that functions are called correctly (e.g. correct number of arguments). They were added to C++ to improve type-checking and were incorporated into C by the standards committee.

Function prototypes can help ensure that functions are called using:

• a compatible return type
• the correct number of arguments
• parameter conversions/promotions

When prototyping function arguments, only the types of the arguments need to be specified. If they are given names, then those names have "function prototype visibility" and are ignored by the compiler. Names used in function prototypes are for documentation purposes only.

##### f() Versus f(void)

In C, `f()` implies a function that takes any number of arguments; where in C++ it indicates a function that takes no arguments.

In C++, `f()` and `f(void)` are equivalent.

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Function Definitions

The function definition contains the statements that comprise a function. The definition of a function is also referred to as its implementation.

Function statements are enclosed in {}'s and are referred to as the function body.

The body of a function consists of zero more variable declarations/definitions and zero or more statements.

Examples:

```   int x(int n1, int n2) {
//this is the function body...
}

void y(float f, char c, int i) {
//this function doesn't return a value; it takes three
//   parameters (a float, a char and an int)
...
if (i) return;
...
}
```
When a function is defined, each parameter, if any, must be specified with a type and a name. Parameter type-name pairs are separated by comma's (these comma's are not the sequence operator).

If the return-type is not specified, then it defaults to `int`. You should get in the habit of always explicitly specifiying the return-type.

Parameters can be thought of as initialized local variables (i.e. space is allocated for them from the stack and they are initialized to the value of the arguments that are passed).

Variables declared inside of a function body are visible only with that block of code. These variables are referred to as a "local" variables.

A function definition can contain multiple return statements; however, many programmers are of the opinion that a function should have only one exit point.

A stub function is a function that contains no statements.

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Function Comment Blocks

Every function should begin with a function comment block. The function comment block contains - at a minimum - the name of the function, a list of arguments that it receives, a description of its return value (if any), and a brief description of what the function does. In addition, any side-effects (or outputs) performed by the function should be documented.

The following is an example function comment block.

```   /*
* name:  stringCompare
* parameters:  char* -- pointer to a string
*              char* -- pointer to a string
* returns:  1 if strings are equal; 0 otherwise
* description:  compares two strings character by character
*               to determine if they are equal
*/
```

Cay Horstmann says...

"The description of a function comment block does not document the implementation but the idea."

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Calling a Function

A function is called by specifying the function's name, followed by a left paren, a comma separated list of arguments (if any) and a right paren. Comma when used in this context is not the sequence operator.

Example.

```   int rv = x(200, 210);
//call the function  x  passing it two values: 200 and 210
//capture the return value from  x  in the variable rv

abort();
//call the function  abort
//no arguments are passed, nor does the function return any value
```

A function call is a sequence point: every EXPR that comprises an argument is evaluated prior to the function being called. The order in which the arguments are evaluated is undefined.

C and C++ are "call-by-value" languages: the arguments are evaluated and their respective values are passed to the function.

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Function Return Value

A function communicates back to the caller by "returning" a value.

The type of value returned by a function (i.e. the return-type) is specified when the function is defined. If the return-type is not specified, then it defaults to `int`.

A function does not have to return a value. In these cases, the return-type `void` is used.

Other points.

• Functions can return at most one value.
• A function returns to the caller by executing a `return` statement.
• Functions can have multiple `return` statements. (Although structured programming purists don't like this.)
• A function returns to the function that called it.

The syntax of the `return` statement is as follows.

```   return;       //used when the return-type of the function is void

return EXPR;

EXPR is evaluated.  The result of the evaluation, if needed,
is converted to the return-type of the function.  For example,
if the return-type of the function is  int  , then

return 3.14;

will cause the 3.14 double to be converted to an int; therefore,
the calling function will be returned the value 3.

Optionally, the return EXPR can be enclosed in parens.

return (EXPR);
return (3.14);           or   return 3.14;
return (EXIT_SUCCESS);   or   return EXIT_SUCCESS;
return (i + 3 * j);      or   return i + 3 * j;
return (i > 4);          or   return i > 4;
```

If a function returns a value, then it is the caller's responsibility to examine the return value.

If a function's return-type is `void`, then `return` statements, if any, cannot have any expressions.

If a function is called that returns a value and the return value is ignored by the caller, then the caller should type-cast the function call to be `(void)`.

```   (void) printf("hello, world\n");
```

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

Lifetime is the period, during execution of a program, in which a variable or function exists (all functions in a program exist at all times during its execution).

Visibility is the portions of the program in which a variable or function can be referenced by name (also referred to as scope (scope units: file, function, block or function prototype).

##### Local and Global Variables

Local variables are declared and/or defined within a block (either a function or a compound statement).

• function parameters are local variables
• uninitialized (except for parameters)
• visible from point of definition to the end of the block
• lifetime is from the point of definition to the end of the block
• memory is allocated from the stack
• memory is de-allocated at the end of the block

Global variables are declared and/or defined outside of any function.

• initialized to zero
• visible from the point they are defined to the end-of-source-file (may be visible in other source files also - see extern)
• memory allocated from the data segment at program startup
• memory is never de-allocated
##### auto

The `auto` storage class indicates that a variable is a local variable and that memory is automatically allocated/de-allocated. By default, local variables are defined to be `auto`; therefore, this storage class is rarely specified.

Using `auto` on a global variable is illegal.

Automatic variables are not initialized to any known value.

##### extern

The `extern` storage class allows a global variable to be visible across multiple source files.

A global variable defined in file A can be accessed in file B if and only if file B contains the following declaration.

```	extern type variable_name;

extern int errno;  /* errno is defined in some other file */
```

Use of `extern` results in a declaration -- not a definition. In other words, an `extern` declaration does not result in the allocation of memory.

It is not legal to initialize an external variable at the time it is declared (i.e. `extern float rate = 5.3;` is illegal).

##### static

When `static` is applied to a global variable, then it limits the scope of an object to the rest of the file (i.e. it cannot be externally declared in other source files).

When `static` is applied to a local variable, then it causes the local variable to remain in existence across function calls providing private, permanent storage within a single function.

When `static` is applied to a function, then the function is visible only to the source file in which is defined (in a way, the function is made "private").

##### register

A register is a high speed memory location located on the CPU.

The `register` storage class is used on local variables that are going to be accessed many times (for example, loop control variables).

• register usage can result in smaller/faster programs
• using `register` is often times ignored by the compiler
• applies only to locals and parameters
• cannot use the address-of operator

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Reference Parameters

C++ passes arguments to functions "by value." This calling mechanism prohibits called functions from modifying the variables defined in the caller functions.

Reference parameters  allows arguments to be passed "by reference" instead of by value. If you pass an argument to a function by reference, then the called function can access that variable.

Passing an argument by reference causes the address of the variable argument to be passed rather than its value; consequently, the called function receives a "pointer" to the variable. Although the called function is dealing with a pointer, pointer notation is not required.

A parameter that is received as a reference becomes an alias for the variable that was passed.

Reference parameters are often used when passing large arguments to a function (e.g. a structure). It is more efficient to by reference than it is to pass by value (less data must be copied).

Suppose we have a function that converts inches to feet and inches. We have a problem: our function needs to return two pieces of information, but is allowed to return only one value. One solution to the problem is to use reference parameters:

```   int convertInches(int totalInches, int& feet);
// the & after the type  int  indicates that the function
// receives a reference to an  int

...

int feet;
int inches = convertInches(80, feet);
// feet is passed by reference; no special notation is needed

...

/**
The function receives the total inches.  The return value
of the function is the inches, and the feet are copied
into the reference parameter supplied as the 2nd argument.
**/

int convertInches(int totalInches, int& feet) {
const int INCHES_PER_FOOT = 12;
feet = totalInches / INCHES_PER_FOOT;
}
```

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Default Function Arguments

Default function arguments can be specified in either the function definition or prototype (but not both). Convention is to specify them in the function prototype.

Only the rightmost arguments can be defaulted. Once a default function argument is used, all remaining arguments must be default arguments.

Default arguments are useful when a function needs more arguments than are necessary to handle simple cases; in particular, functions that construct objects often provide several options for flexibility.

```   Syntax:  data-type function_name(Type param = value);

If  param  is not passed by the caller, then it will be set
to  value  .

Example:

void printReport(char filename[], bool condensed = false);
// one argument is required:  a filename, but the second is a
//     default argument and it defaults to  false  if not passed

printReport("report.out");           //1
printReport("report.out", true);     //2
printReport("report.out", false);    //3
//statements 1 and 3 are equivalent
```

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

Function overloading is the ability to give different functions the same name.

Stroustrup says:

Most often, it is a good idea to give different functions different names, but when some functions conceptually perform the same task on objects of different types, it can be more convenient to give them the same name.
Use descriptive overloaded function names to describe similar operations, not different behaviors.
```   Good:
int max(int, int);        //find max of two ints
float max(float, float);  //find max of two floats

Not so Good:
void draw(Image*);        //draw an image
void draw(Card*);         //draw a card
```
The following is an example of an overloaded function:
```   void print(int), print(double), print(long), print(char),
print(int, int), print(double, double);

char c;
short s;
int i;
float f;

print(c);            // invoke print(char)
print(i);            // invoke print(int)
print(s);            // invoke print(int); s promoted to int
print(f);            // invoke print(double); f promoted to double
print('A');          // invoke print(char); 'A' is a char
print(200);          // invoke print(int); 200 is an int
print(200L);         // invoke print(long); 200L is a long
print(99.9);         // invoke print(double); 99.9 is a double
print(i, i);         // invoke print(int,int)
print(i, 'a');       // invoke print(int,int); 'a' promoted to int
print(s, 'A');       // invoke print(int,int); s - 'A' promoted to int
//! print(1.1L);     // ambiguous -- compiler can't decide
print(200L, i);      // invoke print(int,int);
//! print(i, 3.14);  // ambiguous -- compiler can't decide
```
When  `print()`  is called, the compiler must figure out which of the functions with the name "print" is to be invoked. This is done by comparing the types of the actual arguments with the types of the parameters of all functions called "print". The function with the best match is called; if none exist, then a compile-time error.

Definition:

The  signature  of a function is defined to consist of the name of a function and its ordered set of parameter data types.

Criteria used to determine a match (partial):
1. exact match of function call arguments with an overloaded function signature
2. trivial conversions (exact match after applying promotions to argument data types -- char ==> int, short ==> int, float ==> double)
3. exact match after applying promotions and standard conversions to argument data types (float ==> int, double ==> float)
4. exact match after programmer defined conversions (e.g. typecast)
Note:  `const`  arguments can be distinguished from non-`const` arguments.
```	void foo(const char*);
void foo(char*);

These two functions have different signatures.
```
Return types are not considered in overload resolution.

Functions declared in different scopes do not overload.

If not careful, you can be surprised as to which function is called. It is poor programming practice to redefine library functions (your code may end up calling the correct function, but existing code in the library may end up invoking the wrong function).

Internally, the compiler accomplishes function overloading by  mangling  function names. Function name mangling makes each translated function name unique. A function name is mangled by adding prefixes and suffixes to the the name. The prefixes and suffixes are determined in part by the ordered lists of the function's parameter data types.

```	print(200);             // mangled name: print_Fi
print(float(3.14));     // mangled name: print_Ff
```

C: C++: Java: no yes yes

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Arrays

An array is a collection of individual data values with two characteristics: it is ordered and homogeneous.

The following are some terms commonly used when talking about arrays:

• an element of an array is a single data value
• the type of an array is the data type of its elements
• the location of an array is the location of its first element
• the length of an array is the number of elements in the array
• the size of an array is it's length times the size of an element

An array is homogeneous because each element must be of the same type. For example, an array of int's, an array of float's, an array of char's.

An array is ordered -- it has a 1st element, a 2nd element, a 3rd element, and so on. Array elements are stored in contiguous memory locations.

Just like any other variable, an array must be defined before it is used.

```   Syntax:  element-data-type array-name [ length ];

int intArray[10];
name:  intArray
type:  int
length:  10
size:  10 * sizeof(int)

char someString[32];
name:  someString
type: char
length: 32
size:  32 * sizeof(char)
```

Each element of the array is identified by a numeric value called its index (index numbers always start at 0).

When defining an array, its length must be specified at compile-time. In addition, the specification of the length must be a constant integral EXPR.

```
int i = 10;
/* double salaries[i];   // illegal (not a constant) */
/* char name[15.5];      // illegal (not an integral type) */
const int MAX_ELEMENTS = 10;
short scores[MAX_ELEMENTS];  /* okay in C++, not C */
#define LENGTH 5
float someArrayOfFloats[LENGTH];

```

Typically, array lengths are defined to be manifest constants.

##### Array Initialization

Arrays can be initialized at the time they are defined.

```   int evenNumbers[5] = { 2, 4, 6, 8, 10 };

note:  it is a syntax error if the # of initializers is
greater than the array length (i.e. # of elements)

The elements of the initializer list must be constant
EXPRs.  If the number of initializers is less than the
array length, then remaining elements are set to zero.
```

If an array is initialized when defined, then the length is not needed -- the compiler will set the length depending on the number of initializers. If the length of the array needs to be greater than the number of initializers specified, then the length must be specified.

```   float radioStations[] = { 103.1, 93.3, 100.7 };

radioStations  has a length of 3; to figure out the length
of the array using code:

sizeof(radiostations)  evaluates to the size of the array
and  sizeof(radioStations[0])  evaluates to the size of a
single element of the array (recall, an array size is equal
to the length of the array times the size of the array type)

the following EXPR also works to determine the length of
an array    sizeof(radioStations) / sizeof(float)    but could
result in the defect if the type of the array is changed and
the EXPR is not
```

There is not a convenient mechanism for initializing all elements of an array to a single value (exception: it is easy to set all elements of an array to zero -- `int a[10] = { 0 };`).

For efficiency, locally declared arrays that are initialized at definition may be declared to be `static`.

```   static short tvStations[99] = { 3, 10, 12, 61 };

tvStations  is an array of length 99; elements 0, 1, 2, 3
have non-zero values, whereas elements 4 through 98 equal 0;
the array is initialized once -- at program load time
```

Once an array has been defined, its length (i.e. number of elements) cannot be altered.

Elements of the array are accessed using the unary array operator `[]`.

```   const int LEN = 10;
int a[LEN];

a[3] = 150;  /* set element #4 to 150 */
a[1] = 200;  /* assign the value 200 to element #2 */

if (a[1] == a[3]) /* compare the value of element #2 with element #4*/
```

Array indicies must be integral values, but they are not restricted to being constants.

```   int i, j, k;

a[0] = 100;
a[i] = 150;
a[i * j - k] = 210;
a[a[a[i]]] = 250;
a[rand() % LEN] = 178;
```

The language does not protect against indexing beyond the ends of an array. Typically, if this happens, then a run-time error is encountered.

```   a[-1] = 100;
a[sizeof(a)/sizeof(a[0]) + 2] = 200;
```

Array 'a' cannot be copied to array 'b' using simple assignment.

```   #define LEN 5
int a[LEN] = { 100, 200, 210, 120, 240 }, b[LEN];

/* b = a;   //syntax error -- array name not a lvalue */
for (int i = 0; i < LEN; i++)
b[i] = a[i];
```
##### Arrays and Functions

Arrays are passed to functions "by reference." (Think about the overhead if arrays were passed by value.)

A function that receives an array as a parameter, obtains a constant pointer to the first element of the array.

Unless specifically qualified to be `const`, the function can modify the content of the array.

When a function receives an array as a parameter, it does not know, nor can it figure out, the length or size of the array. In many cases, the caller passes the array length (`size_t`) to the function.

```   void func1(int[]);         //do *not* specify the array length
void func2(const int[]);   //func2() not allowed to modify the array
void func3(int [], int);
#define A_LEN 10
int a[A_LEN];

func1(a);  //using array name w/o [] operator "decays" into a
//constant pointer to the 1st element of the array
func2(a);
func3(a, A_LEN);  //pass the array length to the function
...

void func1(int i[]) {  //again, array length not specified
int len = sizeof(i) / sizeof(i[0]);
// does not work -- sizeof(i) evaluates to the size
// allocated for pointer variables, which is typically
// the sizeof(int)...
...
}

void func2(const int i[]) {
//! i[0] = 100;    //use of  const  implies the content of the
//array cannot be changed...
}

void func3(int i[], int len) {
for (int i = 0; i < len; i++)
//loop through each element of the array
...
}
```

Pointer notation can be used when prototyping and defining functions that receive arrays as parameters.

```   void func1(int*);  //this syntax indicates that the function receives
//a pointer to an array
void func2(const int*);  //array content cannot be modified
```

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

### Pointers

A pointer is a variable whose value is an address of another variable.

• pointers are referred to as derived data types
• a pointer is a variable (it has a name, and it points to a particular type of data)
• the amount of space allocated for a pointer variable is typically the size allocated for an `int`
• pointer variables are assigned address values obtained using the address-of operator `&`
• local pointer variables are uninitialized
##### Defining and Initializing Pointer Variables
When defining a variable, prefixing the variable's name with an asterik `*` causes the variable to be a pointer.

```   int* iptr;   /*define variable iptr that will point to an int variable*/
float * fptr; /*define variable fptr that will point to a float variable*/
char *cptr;  /*define variable cptr that will point to a character*/
int i, j;
float f;
char c;

iptr = &i;  /*assign the address-of variable 'i' to iptr*/
fptr = &f;  /*assign the address-of variable 'f' to fptr*/
cptr = &c;  /*assign the address-of variable 'c' to cptr*/
int* iptr2 = &j; /*define and initialize an int pointer*/
iptr = iptr2;  /*now iptr points to the variable 'j'*/

note:  Placement of the  *  when defining a pointer variable is
a matter of style -- I like to place the  *  next to the
data type, but others prefer to place it next to the
variable name.  Placing it next to the data type does
require caution when multiple variables are defined on
the same declaration statement.  Example:

int* ip1, ip2;
// ip1  is a pointer to an  int  , but  ip2  is a
regular  int

int* ip1, *ip2;
// ip1  and  ip2  are both pointers to an  int
```

The address-of operator only applies to objects in memory: variables and array elements.

Locally defined non-static pointers, unless explicitly initialized, are garbage and using them without initialization can cause a program to execute incorrectly (or abort).

Global and statically defined pointers are initialized to the `NULL` pointer.

##### Accessing Data Using Pointers

The unary operator `*` is the indirection or dereferencing operator; when applied to a pointer, it accesses the object the pointer points to.

```   int i = 200;
int* iptr = &i;

cout << *iptr;    /*prints 200 -- the value of 'i' which is the object
iptr points to*/
```
##### Pointers and Function Arguments

Since C passes arguments to functions by value, there is no way for the called function to alter a variable in the calling function. A way to obtain the desired effect is for the calling program to pass pointers to the values to be changed.

```   void swap(int*, int*);

int i, j;

swap(&i, &j);

void swap(int* a, int* b) {
int tmp = *a;
*a = *b;
*b = tmp;
}
```

Using pointers is similar to using reference variables; however, reference variables are part of C++ and they are not part of C.

Advantage of using reference variables over pointers.

• cleaner syntax

##### Introduction to Pointers and Arrays

There is a strong relationship between pointers and arrays.

When an array name is used by itself, it evaluates to a constant pointer to the first element of the array.

Everywhere you use `arrayName[index]` you can use `*(ptr + index)` (assuming `ptr` points to some part of the array).

```   int scores[10];

scores[0] = 2;      // or  *scores = 2
scores[1] = 3;      // or  *(scores + 1) = 3
*(scores + 2) = 5;  // or  scores[2] = 5
```

{TopOfPage} {Tutorial} {online IDEs: CodingGround | CPP.sh | jdoodle} {C at MIT} {GDT::C/C++ Resource}

Home Previous Next