A Simple Program Using Primitive Arrays

This program reads in a list of numbers from std::cin, and then calculates a few statistics about them.

#include <iostream>
#include <algorithm>

int main() {
    double values[100];
    size_t numValues = 0;

    while (true) {
        double value;
        std::cin >> value;
        if (!std::cin.good()) {
            break;
        }
        values[numValues] = value;
        ++numValues;
    }

    double total = 0.0;
    for (auto p = values; p != values+numValues; ++p) {
        total += *p;
    }

    std::cout << "Read " << numValues << " values" 
              << ", total " << total
              << ", average " << total/numValues << std::endl;

    std::sort(values,values+numValues);
    std::cout << "Min is " << values[0]
              << ", max is " << values[numValues-1]
              << ", median is " << values[numValues/2] << std::endl;

    return 0;
}

The ASCII-cast below shows the program being compiled and run:

Like a video, you can pause, rewind, and replay the ASCII-cast as often as you like.

Our code set a fixed size for the array (100 elements), so if our program tries to read more elements than that limit at runtime, it goes out of bounds, attempting to read memory outside the array.

When our code tried to read 500 elements from its 100-element array, it caused a segmentation fault because it corrupted the stack, which caused problems for the hidden system function that called main.

When we tried to make our code read 50,000 elements from its 100-element array, the program not only overran the stack, but attempted to access memory outside the bounds of the memory it was given by the operating system, causing a segmentation fault error.

The C++ standard provides a full-featured alternative to primitive arrays—std::vector—that is much easier to use, just like the CoordVector class you wrote in the Maze assignment, but working on any type of data, not just Coords.

CS 70 is about understanding how data structures work (learning C++ is a secondary goal). When you have arrays that can hold arbitrary numbers of things, growing as needed, something has to happen to make that possible. You've seen enough by now to understand how that all works behind the scenes and in your code.

(When logged in, completion status appears here.)