Content deleted Content added
Reversed the main premise of this passage. Automated object pools are possible in C++ via smart pointers; Only manual possible in Java/C# as finalizers are really a bad idea. |
Fixed up a grammatical error and added suggestion to use try/finally |
||
Line 34:
== Implementation ==
Object pools can be implemented in an automated fashion in languages like C++ via smart pointers. In the constructor of the smart pointer - an object can be requested from the pool and in the destructor of the smart pointer - the object can be released back to the pool. In garbage collected languages, where there are no destructors (which are guaranteed to be called as part of a stack unwind) - object pools MUST be implemented in a manual fashion, by explicitly requesting an object from the [[Factory (object-oriented programming)|factory]] and returning the object
Manual object pools are simple to implement, but harder to use, as they require [[manual memory management]] of pool objects.
|