vector of fstream

[Marc Schellens]

I have (or better had) a class wich contains
a fstream (as a private member).
I made a vector of this class.
When I resize() the vector I got several error messages,
about some stuff being private int that context.
Is this gcc (3.2) specific or is there a 'official' reason for this?
thanks,
marc

 

[Jim Fischer]

I have (or better had) a class wich contains
a fstream (as a private member).
I made a vector of this class.
When I resize() the vector I got several error messages,
about some stuff being private int that context.
Is this gcc (3.2) specific or is there a 'official' reason for this?

The C++ iostreams classes are neither CopyConstructable nor Assignable.
So iostream objects cannot reside in objects / containers that require
these properties (e.g., STL containers). For example:

struct X { std:fstream out; }

X x1, x2;

// Invoke 'X::X(const X&)' (i.e., class X's copy constructor)
X x3(x2); // ERROR -- member 'out' is not copyable

// Invoke 'X:perator=(const X&)'
x1 = x2; // ERROR -- member 'out' is not assignable

 

[John Harrison]

The C++ iostreams classes are neither CopyConstructable nor Assignable.
So iostream objects cannot reside in objects / containers that require
these properties (e.g., STL containers). For example:

struct X { std:fstream out; }

X x1, x2;

// Invoke 'X::X(const X&)' (i.e., class X's copy constructor)
X x3(x2); // ERROR -- member 'out' is not copyable

// Invoke 'X:perator=(const X&)'
x1 = x2; // ERROR -- member 'out' is not assignable

All that is true, but the OP has an fstream in a class, and the class was
put in a vector. So the OP can get around this problem if he can define a
copy constructor and assignment operator for his class. Admittedly this
might be difficult.

john