Dirk Reiners wrote: > Hi Marcus, > > Marcus Lindblom wrote: >> Can't we just settle for _one_ name per type, please? (And I vote for >> RefPtr, which is consistent with earlier OpenSGs and other APIs as well) >> > I can see your point, and I'm a little torn. The problem is that we do > have two kinds of refptrs, depending on whether you want changes to go > into the ChangeList or not, so we need two names that make clear what > the pointer does, and we came up with RecPtr and UnrecPtr. I hope it's > clear which is which ;). > > So if we want to use RefPtr instead of RecPtr we need to have a sensible > replacement for the UnrecPtr, and I'm not sure if I like UnrecRefPtr or > URefPtr. > > Other ideas?
Another option would be to use the names RefPtr and UnrecPtr, where RefPtr is what you use in 99% of the cases as a user? IIUC, UnrecPtr is something users wouldn't worry about much. It is a special case anyway, since there's no MTUnrecPtr? (Or is there? ;) Otherwise I'd be fine with RecPtr too, my feelings aren't that strong one way or another (Except for going both ways..), even though I'd prefer RefPtr on count of it being a common & known name for pointers. Cheers, /Marcus ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
