int sillyFunction (int randomNUMBER){    int derived_octagon = randomNUMBER * 8;    return derived_octagon;}// now you wouldn''t normally use a pointer to pass an integer// to a function would you? no of course not. an int (integer)// is only 4 bytes. so the compiler can copy that variable and // not suck up too much memory. BUT what about this??class CCrazyClass{      public:    long int distance_in_space;  // 4 bytes    double maximum_velocity;     // 8 bytes    string name_of_shuttle;      // x bytes    double shuttle_weight;       // 8 bytes    short number_of_tanks;       // 2 bytes    float time_in_space;         // 4 bytes    string liftoff_base;         // x bytes    string landing_base;         // x bytes     // functions go here         // haha bytes!}// now if you wanted to pass that class to a function you''ll be// passing around at LEAST 26 bytes of data (and that''s assuming// the class variables are aligned correctly). now a program// will have several classes and structs like that. you don''t // want to be copying data like that from function to function// so you can pass a pointer to it. just like this!CCrazyClass FirstShuttle;CCrazyClass *RefShuttle = &FirstShuttle// now RefShuttle has direct access to FirstShuttle.void displayShuttleReadings (CCrazyClass *RefShuttle){    RefShuttle.distance_in_space = 28900;    RefShuttle.name_of_shuttle = "SSExplorer";    // blah blah, rest goes here}// now in case you''re wondering you did not just copy the whole// 26+ bytes from the class into the function. all you did was// copy 4 bytes. All pointers no matter what their datatype are// 4 bytes. And they are still able to access the same data// from the variable they point to (check for the declaration)// (access the data directly