Hi, On Fri, 2008-06-20 at 08:50 -0500, Carsten Neumann wrote: > Hi, > > Gerrit Voss wrote: > > On Thu, 2008-06-19 at 18:06 -0500, Carsten Neumann wrote: > >> can somebody remember or think of a reason for the GraphOp d'tor being > >> protected? > > > > Because they were move to be reference counted so that the don't leak > > memory. >
> ok. > Hm, can we not simply suggest users store these with boost:shared_ptr? > I think we should try and reduce the number of ref counting schemes the > user deals with (currently: MemoryObject, FieldContainer, > boost::shared_ptr for the handles). > Grepp'ing through the code, I can find the following uses of MemoryObject: > > - SharedObject > - MPBase > - ClusterNetwork > - ChangeList > - GraphOp > - GraphOpSeq > - StatCollector > - TextFace > - NavigatorEngine > > boost:shared_ptr is currently used for the FieldHandles and in two files > of Contrib/BackgroundLoader > > So, what does everybody think about moving (at least) GraphOp, > GraphOpSeq, StatCollector, TextFace and NavigatorEngine to shared_ptr ? I would more tend to move it to our refcount ptrs. I'll give it a try because I need refcount ptrs for helper objects for a loader I was just wasting some time on (openflight). kind regards, gerrit ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
