Pointers and arrays in C++ - Time & Space Complexity
When working with pointers and arrays, it's important to know how the time to access or process elements changes as the array size grows.
We want to understand how the number of steps grows when we use pointers to traverse arrays.
Analyze the time complexity of the following code snippet.
void printArray(int* arr, int size) {
for (int i = 0; i < size; i++) {
std::cout << *(arr + i) << " ";
}
std::cout << std::endl;
}
This code prints all elements of an integer array using a pointer.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Accessing each element via pointer arithmetic and printing it.
- How many times: Exactly once for each element, so
sizetimes.
As the array size grows, the number of steps to print all elements grows directly with it.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 element accesses and prints |
| 100 | 100 element accesses and prints |
| 1000 | 1000 element accesses and prints |
Pattern observation: Doubling the array size doubles the work done.
Time Complexity: O(n)
This means the time to complete the task grows in direct proportion to the number of elements.
[X] Wrong: "Using pointers makes accessing elements faster, so time complexity is constant."
[OK] Correct: While pointers can be efficient, accessing each element still requires a step, so the total time grows with the number of elements.
Understanding how pointer traversal scales helps you explain array processing clearly and confidently in interviews.
"What if we used a nested loop to compare each element with every other element? How would the time complexity change?"
Practice
Solution
Step 1: Understand array name behavior
In C++, the name of an array acts as a pointer to its first element, not the whole array or size.Step 2: Confirm pointer usage
This pointer can be used to access elements by pointer arithmetic or indexing.Final Answer:
A pointer to the first element of the array -> Option DQuick Check:
Array name = pointer to first element [OK]
- Thinking array name stores size
- Confusing array name with last element
- Assuming array name copies data
arr?Solution
Step 1: Understand pointer declaration
To declare a pointer to an integer, useint *ptr. The array namearracts as a pointer to its first element.Step 2: Assign pointer correctly
Assigningptr = arr;sets the pointer to the first element's address. Using&arrgives the address of the whole array, which has a different type.Final Answer:
int *ptr = arr; -> Option CQuick Check:
Pointer to first element = int *ptr = arr [OK]
- Using &arr instead of arr for pointer
- Declaring pointer as int instead of int*
- Assigning pointer without *
int arr[] = {10, 20, 30};
int *p = arr;
std::cout << *(p + 1) << std::endl;Solution
Step 1: Understand pointer arithmetic
Pointerppoints toarr[0]. Adding 1 moves pointer toarr[1].Step 2: Dereference pointer at new position
Dereferencing*(p + 1)gives the value atarr[1], which is 20.Final Answer:
20 -> Option AQuick Check:
*(p + 1) = arr[1] = 20 [OK]
- Confusing pointer arithmetic with addition of values
- Dereferencing pointer without offset
- Expecting compilation error
int arr[3] = {1, 2, 3};
int *p = &arr;
std::cout << *(p + 2) << std::endl;Solution
Step 1: Analyze pointer assignment
arris an array name acting as pointer to first element.&arris address of whole array, typeint (*)[3], incompatible withint *.Step 2: Correct pointer assignment
Assigningint *p = arr;is correct to point to first element. Using&arrcauses type mismatch and incorrect pointer arithmetic.Final Answer:
Incorrect pointer assignment: &arr should be arr -> Option BQuick Check:
Use arr, not &arr, for int* pointer [OK]
- Using &arr instead of arr for int*
- Ignoring pointer type mismatch warnings
- Assuming &arr points to first element
int arr[] = {5, 10, 15, 20};
int *p = arr + 1;
std::cout << p[2] << std::endl;Solution
Step 1: Understand pointer initialization
p = arr + 1;points toarr[1], which is 10.Step 2: Access element using pointer indexing
p[2]means *(p + 2), which points toarr[3](1 + 2 = 3), value 20.Final Answer:
20 -> Option AQuick Check:
p[2] = arr[3] = 20 [OK]
- Confusing p[2] with arr[2]
- Forgetting pointer offset starts at arr + 1
- Assuming p[2] is out of bounds
Ready to prove it?
Pass the test and this pattern moves unknown
