Content deleted Content added
→top: split off benefits, correct, link to slab |
m →Implementation: fix ref |
||
Line 26:
== Implementation ==
Object pools can be implemented manually, by explicitly requesting an object from a [[Factory (object-oriented programming)|factory]] and returning the object via calling a dispose method, as in the [[dispose pattern]]. Alternatively, in garbage-collected languages, object pools can be implemented automatically for a [[Class (computer programming)|class]] by having the [[Constructor (object-oriented programming)|constructor]] return an object from the pool, and the [[finalizer]] return an object to the pool, using [[object resurrection]] to return the object to life.{{sfn|name=pronet129|Goldshtein|Zurbalev|Flatow|2012|p=[http://books.google.co.jp/books?id=D3J58cs-i44C&pg=PA129&q=resurrection#v=onepage&q=resurrection 129]}} Note that automatic object pools are not possible if using a [[Destructor (computer programming)|destructor]], as this guarantees destruction of the object.
Manual object pools are simple to implement, but harder to use, as they require [[manual memory management]] of pool objects. By contrast, automatic object pools are easy to use – indeed, transparent – but require language support for multiple finalization and significantly complicate [[garbage collection]]; automatic object pools are one of the few standard applications of object resurrection.{{sfn|name=pronet129}}
| |||