Hi, On Tue, 2010-06-29 at 17:50 -0500, Carsten Neumann wrote: > Hello Gerrit, > > yes, but how do you know which RefCountPolicy to use? The main > motivation for PointerMFieldBase was not having to know the type or ref > count details of the specific field. I had thought the (limited) set of > member functions would be safe, but had overlooked the > RefCountPolicy::validate() case. > Do you propose to unconditionally go through > WeakRefCountPolicy::validate() ?
yes, if I'm not totally mistaken, as we don't allow to modifiy the field at this level validating the return value through the WeakRefCountPolicy should be enough (that's what the SField is doing on getValue). > > I fixed the SField part already so that should cover most of > > the use cases (I actually don't remember having a weak mfield > > somewhere). > > True, but I'd prefer fixing it for MField anyway ;) > > > I just have to find the time ;) > > I can take care of the implementation, just wanted to be sure first what > the preferred way to solve this is - of course carefully thinking this > through takes time too ;) fine with me. kind regards gerrit ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
