Projects/Marble/GeoData/PointerVsImplicitShare

< Projects‎ | Marble‎ | GeoData
Revision as of 14:04, 31 March 2010 by Bholst (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Implicit sharing and storing objects as value is very reasonable for basic data as QStrings, but there are reasonable doubts regarding Placemarks and other GeoData. There are some possibilities:

  • Don't use implicit sharing at all and store all objects on the heap with a pointer to it.
  • Use implicit sharing and storing as value for GeoDataCoordinates only.
  • Use implicit sharing and storing as value for all GeoData classes.

To find out which is the wisest I try to look at every single class:


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal