#include <array>
#include <iostream>
using namespace std;
struct SimpleDebugger
{
SimpleDebugger(int val = 0) : x(val) {
cout << "created" << endl;
}
SimpleDebugger(const SimpleDebugger &that) : x(that.x) {
cout << "copied" << endl;
}
~SimpleDebugger() {
cout << "killed!" << endl;
}
int getX() const {
return x;
}
void setX(int val) {
x = val;
}
private:
int x;
};
array<SimpleDebugger, 3> getInts(int i)
{
array<SimpleDebugger, 3> a;
a[0].setX(i);
a[1].setX(i + 1);
a[2].setX(i + 2);
cout << "closing getInts" << endl;
return a;
}
SimpleDebugger (*getIntsArray(int i)) [3] {
typedef SimpleDebugger SimpleDebugger3ElemArray [3];
SimpleDebugger3ElemArray *sd = new SimpleDebugger3ElemArray[1];
(*sd)[0].setX(i);
(*sd)[1].setX(i + 1);
(*sd)[2].setX(i + 2);
cout << "closing getIntsArray" << endl;
return sd;
}
ostream& operator << (ostream& os, const SimpleDebugger &sd) {
return (cout << sd.getX());
}
int main() {
auto x = getInts(5);
cout << "std::array = " << x[0] << x[1] << x[2] << endl;
auto y = getIntsArray(8);
cout << "Raw array = " << (*y)[0] << (*y)[1] << (*y)[2] << endl;
delete [] y;
}
Output
created
created
created
closing getInts
std::array = 567
created
created
created
closing getIntsArray
Raw array = 8910
killed!
killed!
killed!
killed!
killed!
killed!
I tried this above program to see how convenient it is to use std::array
over raw arrays, I know that avoiding old-style arrays is good style and even better is to use std::vector
.
I'd like to know what happens under the hood in case of std::array
, when the function getInts()
returns. In case of the raw arrays, I know that it's a pointer copy and the onus of cleaning it up falls on the callee. In std::array
this doesn't happen, but how does it internally store the data and how does the copy happen?