From: OpenSG <tra...@vr...> - 2009-05-15 22:30:55
|
#207: MF-fields ought to be fully std::container compliant --------------------------------+------------------------------------------- Reporter: marcusl | Owner: unassigned Type: defect | Status: closed Priority: minor | Milestone: Component: System | Version: 1.8 Resolution: fixed | Keywords: Estimated_completion: | --------------------------------+------------------------------------------- Changes (by cneumann): * status: new => closed * resolution: => fixed Old description: > Often, one has to to MFFoo.getValues() to make generic algorithms from > STL work with these fields. > > > Either inheriting publically, or forwarding _all_ typedefs and member > functions from the underlying std::vector type ought to fix this. > > > I've been specifically missing value_type & all insert/erase variants, > but there might be more. New description: Often, one has to to MFFoo.getValues() to make generic algorithms from STL work with these fields. Either inheriting publically, or forwarding _all_ typedefs and member functions from the underlying std::vector type ought to fix this. I've been specifically missing value_type & all insert/erase variants, but there might be more. Comment: I think we cover all functions nowadays. Closing. -- Ticket URL: <http://opensg.vrsource.org/trac/ticket/207#comment:1> OpenSG <http://opensg.vrsource.org> OpenSG Project |