From: Felipe Magno de Almeida (felipe.almeida_at_[hidden])
Date: 2005-03-10 15:09:59
Thorsten Ottosen wrote:
> "Felipe Magno de Almeida" <felipe.almeida_at_[hidden]> wrote in message
> | Thorsten Ottosen wrote:
> | > "Felipe Magno de Almeida" <felipe.almeida_at_[hidden]> wrote in message
> | > news:4230862D.6040003_at_ic.unicamp.br...
> yes, but this is no ordinary std::vector. std::vector is for self-contained
> value types; boost::ptr_vector is for pointers whose life-time
> must be managed.
> | boost::vector<A> vector1, vector2;
> | vector1 = vector2;
> boost::ptr_vector don't have an assignment operator; it is not Assignable nor
> you must clone or release the container:
> vector1 = vector2.clone();
> vector1 = vector2.release();
I see, but it makes impossible for use ptr_containers inside other
containers. Isnt this too restrictive?
Cant they be implemented in terms of these?
There were a discussion about this before? So that I can know the
what I was think is that the copy constructor and the assignment
operator could be part of the clone policy. Maybe Im wrong.
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Felipe Magno de Almeida UIN: 2113442 email: felipe.almeida at ic unicamp br, felipe.m.almeida at gmail com, felipe at synergy com I am a C, modern C++, MFC, ODBC, Windows Services, MAPI developer from synergy, and Computer Science student from State University of Campinas(UNICAMP). To know more about: Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br current work: http://www.mintercept.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk