Hi Dirk! Sorry about upsetting you so with my workaround...
> > My 0.02 SEK on design of reference counting systems is that the > > preffered way is to disallow users to change the ref-count explicitly > > (i.e. encapsulate this in the well-behaved RefPtr-class, and similar > > structures) but allow them to access this for reading (so that > > deviations from expected ref-count can be checked, in case of unwanted > > cycles and such). Manual ref-counting is, from my experience, quite > > error-prone. However, I don't know if this is an option for the OpenSG > > user base, as they might be doing a lot of explicit add/sub-refs. > > I'm hoping to motivate people to move over to RefPtr for use in > applications and away from explicit add/subRefs. For backwards > compatibility they will stay around for a while, though. > > So, everybody feel motivated to use RefPtrs to store data in your > apps! :) > I use the RefPtr whenever I get a chance. But I would like to see some more operators defined, so that I can use it even more. Like <, so that it can be inserted in a map or a set. I could write my own but it would be nicer if it was defined in the RefPtr class. And also some operators for comparisons to NullFC and other FieldContainerPtrs. What do you think about that? Regards Fredrik ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
