Changeset 10555 for code/branches/core7/src/libraries/core/CoreStaticInitializationHandler.cc

Timestamp:

Aug 29, 2015, 5:35:59 PM (9 years ago)

Author:

landauf

Message:

renamed SmartPtr to StrongPtr (now we have weak and strong pointers)

File:

• code/branches/core7/src/libraries/core/CoreStaticInitializationHandler.cc (modified) (1 diff)

code/branches/core7/src/libraries/core/CoreStaticInitializationHandler.cc

@@ -102 +102 @@
             identifiers.insert(&static_cast<StaticallyInitializedIdentifier*>(*it)->getIdentifier());
 
-        // destroy objects. some objects may survive this at first because they still have smart pointers pointing at them. this is
-        // ok as long as those smart pointers are held by objects that are also about to be destroyed in the same loop. this means
-        // that objects within one module may reference each other by smart pointers. but it is not allowed that objects from another
-        // module (which is not unloaded) uses smart pointers to point at objects inside the unloaded module. this will lead to a crash.
+        // destroy objects. some objects may survive this at first because they still have strong pointers pointing at them. this is
+        // ok as long as those strong pointers are held by objects that are also about to be destroyed in the same loop. this means
+        // that objects within one module may reference each other by strong pointers. but it is not allowed that objects from another
+        // module (which is not unloaded) uses strong pointers to point at objects inside the unloaded module. this will lead to a crash.
         for (std::set<Identifier*>::iterator it = identifiers.begin(); it != identifiers.end(); ++it)
             (*it)->destroyObjects();
 
-        // check if all objects were really destroyed. this is not the case if an object is referenced by a smart pointer from another
+        // check if all objects were really destroyed. this is not the case if an object is referenced by a strong pointer from another
         // module (or if two objects inside this module reference each other). this will lead to a crash and must be fixed (e.g. by
         // changing object dependencies; or by changing the logic that allows modules to be unloaded).