9.8 — Introduction to pointers

In lesson 1.3 -- a first look at variables, we noted that a variable is a name for a piece of memory that holds a value. When our program instantiates a variable, a free memory address is automatically assigned to the variable, and any value we assign to the variable is stored in this memory address.

For example:

When this statement is executed by the CPU, a piece of memory from RAM will be set aside. For the sake of example, let’s say that the variable x is assigned memory location 140. Whenever the program sees the variable x in an expression or statement, it knows that it should look in memory location 140 to get the value.

The nice thing about variables is that we don’t need to worry about what specific memory address is assigned. We just refer to the variable by its given identifier, and the compiler translates this name into the appropriately assigned memory address.

However, this approach has some limitations, which we’ll discuss in this and future lessons.

The address-of operator (&)

The address-of operator (&) allows us to see what memory address is assigned to a variable. This is pretty straightforward:

On the author’s machine, the above program printed:


Note: Although the address-of operator looks just like the bitwise-and operator, you can distinguish them because the address-of operator is unary, whereas the bitwise-and operator is binary.

The indirection operator (*)

Getting the address of a variable isn’t very useful by itself.

The indirection operator (*) (also called dereference operator) allows us to access the value at a particular address:

On the author’s machine, the above program printed:


Note: Although the indirection operator looks just like the multiplication operator, you can distinguish them because the indirection operator is unary, whereas the multiplication operator is binary.


With the address-of operator and indirection operators now added to our toolkits, we can now talk about pointers. A pointer is a variable that holds a memory address as its value.

Pointers are typically seen as one of the most confusing parts of the C++ language, but they’re surprisingly simple when explained properly.

Declaring a pointer

Pointer variables are declared just like normal variables, only with an asterisk between the data type and the variable name. Note that this asterisk is not an indirection. It is part of the pointer declaration syntax.

Syntactically, C++ will accept the asterisk next to the data type, next to the variable name, or even in the middle.

Best practice

When declaring a pointer variable, put the asterisk next to the type to make it easier to distinguish it from an indirection.

Author's note

The above “Best Practice” is currently not consistently used in the lessons. Feel free to point out occurrences of asterisks next to the variable name in the comment section.

Just like normal variables, pointers are not initialized when declared. If not initialized with a value, they will contain garbage.

One note on pointer nomenclature: “X pointer” (where X is some type) is a commonly used shorthand for “pointer to an X”. So when we say, “an integer pointer”, we really mean “a pointer to an integer”.

Assigning a value to a pointer

Since pointers only hold addresses, when we assign a value to a pointer, that value has to be an address. One of the most common things to do with pointers is have them hold the address of a different variable.

To get the address of a variable, we use the address-of operator:

Conceptually, you can think of the above snippet like this:

This is where pointers get their name from -- ptr is holding the address of variable value, so we say that ptr is “pointing to” v.

It is also easy to see using code:

On the author’s machine, this printed:


The type of the pointer has to match the type of the variable being pointed to:

Note that the following is also not legal:

This is because pointers can only hold addresses, and the integer literal 5 does not have a memory address. If you try this, the compiler will tell you it cannot convert an integer to an integer pointer.

C++ will also not allow you to directly convert literal memory addresses to a pointer:

The address-of operator returns a pointer

It’s worth noting that the address-of operator (&) doesn’t return the address of its operand as a literal. Instead, it returns a pointer containing the address of the operand, whose type is derived from the argument (e.g. taking the address of an int will return the address in an int pointer).

We can see this in the following example:

On Visual Studio 2013, this printed:

int *

(With gcc, this prints “pi” (pointer to int) instead).

This pointer can then be printed or assigned as desired.

Indirection through pointers

Once we have a pointer variable pointing at something, the other common thing to do with it is indirection through the pointer to get the value of what it’s pointing at. Indirection through a pointer evaluates to the contents of the address it is pointing to.

On the author’s machine, this printed:


This is why pointers must have a type. Without a type, when indirecting through a pointer, the pointer wouldn’t know how to interpret the contents it was pointing to. It’s also why the type of the pointer and the variable address it’s being assigned to must match. If they did not, indirection through the pointer would misinterpret the bits as a different type.

Once assigned, a pointer value can be reassigned to another value:

When the address of variable value is assigned to ptr, the following are true:

  • ptr is the same as &value
  • *ptr is treated the same as value

Because *ptr is treated the same as value, you can assign values to it just as if it were variable value! The following program prints 7:

A warning about indirection through invalid pointers

Pointers in C++ are inherently unsafe, and improper pointer usage is one of the best ways to crash your application.

During indirection through a pointer, the application attempts to go to the memory location that is stored in the pointer and retrieve the contents of memory. For security reasons, modern operating systems sandbox applications to prevent them from improperly interacting with other applications, and to protect the stability of the operating system itself. If an application tries to access a memory location not allocated to it by the operating system, the operating system may shut down the application.

The following program illustrates this, and will probably crash when you run it (go ahead, try it, you won’t harm your machine):

The size of pointers

The size of a pointer is dependent upon the architecture the executable is compiled for -- a 32-bit executable uses 32-bit memory addresses -- consequently, a pointer on a 32-bit machine is 32 bits (4 bytes). With a 64-bit executable, a pointer would be 64 bits (8 bytes). Note that this is true regardless of the size of the object being pointed to:

As you can see, the size of the pointer is always the same. This is because a pointer is just a memory address, and the number of bits needed to access a memory address on a given machine is always constant.

What good are pointers?

At this point, pointers may seem a little silly, academic, or obtuse. Why use a pointer if we can just use the original variable?

It turns out that pointers are useful in many different cases:

1) Arrays are implemented using pointers. Pointers can be used to iterate through an array (as an alternative to array indices) (covered in lesson 9.24 -- Introduction to iterators).
2) They are the only way you can dynamically allocate memory in C++ (covered in lesson 9.13 -- Dynamic memory allocation with new and delete). This is by far the most common use case for pointers.
3) They can be used to pass a function as a parameter to another function (covered in lesson 10.9 -- Function Pointers).
4) They can be used to achieve polymorphism when dealing with inheritance (covered in lesson 18.1 -- Pointers and references to the base class of derived objects).
5) They can be used to have one struct/class point at another struct/class, to form a chain. This is useful in some more advanced data structures, such as linked lists and trees.

So there is actually a surprising number of uses for pointers. But don’t worry if you don’t understand what most of these are yet. Now that you understand what pointers are at a basic level, we can start taking an in-depth look at the various cases in which they’re useful, which we’ll do in subsequent lessons.


Pointers are variables that hold a memory address. The value they are pointing to can be accessed using the indirection operator (*). Indirection through a garbage pointer causes undefined behavior.

Quiz time

Question #1

What values does this program print? Assume a short is 2 bytes, and a 32-bit machine.

Show Solution

Question #2

What’s wrong with this snippet of code?

Show Solution

9.9 -- Null pointers
9.7 -- An introduction to std::string_view

313 comments to 9.8 — Introduction to pointers

  • Shareware

    The memory address 0012FF7C is 128bit no? Each character has 16 possible values and there's 8 values = 128bit? But these computers don't exist yet!

    • Alex

      Nope. Each character is a hex value, which has 16 possible values, but that only takes 4 bits to represent. 4 bits * 8 characters = 32 bits.

  • Tobito

    • Alex

      Because std::cout and operator << assume object of type char* are null-terminated C-style strings. In this case, you're giving it a single, non-terminated char, so it just keeps printing stuff until it happens upon a random termination character.

  • kk

    Running and compiling the 'crash' program doesn't crash it.

    I compiled it with g++ using the following command on linux:

    I always get the following output:

    Is this normal? Why does that happen?

    • Alex

      No idea. The nature of undefined behavior is such that it could do anything. Crashing is definitely the most common, but it's not a guarantee.

  • Andreas Krug

    Small suggestion: In lesson 1.3 -- Introduction to variables  instead of  In lesson 1.3 -- a first look at variables

  • Legna

    "The size of a pointer is dependent upon the architecture the executable is compiled for -- a 32-bit executable uses 32-bit memory addresses -- consequently, a pointer on a 32-bit machine is 32 bits (4 bytes). With a 64-bit executable, a pointer would be 64 bits (8 bytes)"

    Hi, I'm using a 64-bit processor and yet when I use sizeof() on a pointer it prints '4'. Why is not saying '8'?

  • Adam C.

    Because strings and Chars were a few chapters ago, I wanted to see what pointers would do. When I try to use a char pointer the output was not what I was expected. Other data types; int, double, etc. work as expected.

    • nascardriver

      `std::cout` treats `char*` as strings. If you want to print the address, you need to cast it to `void*`.

      `string1` is a non-`const` pointer to a `const` string. You're overriding the pointer, not the string.

  • Sahil

    Best Practice:
    When declaring a pointer variable, put the asterisk next to the type to make it easier to distinguish it from an indirection.

    Best Practice:
    When declaring a pointer variable, put the asterisk next to the variable name.

    These kind of contradict themselves right?? What should we be doing? I am used to the 2nd way i.e. int *ptr{};

  • Waldo Lemmer

    When my program attempts to access an uninitialized pointer, it crashes (of course), and the error code for that crash (as shown in Event Viewer) is c0000005. This is the same error code that I got in games when my memory was unstable, and the error message next to it was often "Access violation". I know what that error message means now!

    Now I just need to figure out how memory editors like Cheat Engine work. Facinating stuff! :D

    Section "What good are pointers?":
    > So there are actually a surprising number of uses for pointers.
    I think "are" should be "is", as "number" is singular.

    This lesson is very interesting and well explained :)

Leave a Comment

Put all code inside code tags: [code]your code here[/code]