Talk:Object pool pattern: Difference between revisions

Revision as of 21:36, 10 April 2008

Latest revision as of 11:28, 30 January 2024

(11 intermediate revisions by 10 users not shown)

Line 1:

{{old XfD multi |date=6 October 2005 |result='''merge with [[Object pool]]''' |page=Wikipedia:Articles for deletion/Object cesspool}}

{{WikiProject banner shell|class=Start|

{{WikiProject Computer science|importance=}}

|}}

==comment==

My English writing skills aren't up to much, so I can't really clean up this article, but I'm happy to monitor the technical content, and ensure that a rewrite by someone with English skills (but no tech knowledge) doesn't get the tech wrong.

Line 4 ⟶ 10:

==Moved from [[Talk:Object cesspool]]==

{| class="messagebox standard-talk"

|-

| style="text-align: center" |This article was nominated for '''''[[Wikipedia:Deletion policy|deletion]]''''' on 6 October 2005. The result of the discussion was <b>merge with [[Object pool]]</b>. An archived record of this discussion can be found [[Wikipedia:Articles for deletion/Object cesspool|here]].

|}

This article has little value. It might as well be called "I had some bugs in my code that were interesting to me, and I came up with a cute name for it."

Line 26:

==Definition of an Object Pool==

I've added some external references and links. There seems to be some confusion over what exactly an object pool is. For example, this [http://www.awprofessional.com/articles/article.asp?p=30309&seqNum=3&rl=1 Inform IT article] classifies it as a memory pattern rather than as a creational pattern, and describes it slightly differently as "Pool Allocation Pattern works well by creating pools of objects, created at startup, available to clients upon request", whereas many other sources describe this pattern more as a recycling method that can still dynamically allocate objects on demand if one isn't already available in the pool. e.g., from the EuroPlos conference paper: "To increase efficiency, the resource pool eagerly acquires a static number of resources after creation. If the demand exceeds the available resources in the pool, it lazily acquires more resources." [[User:Saigyo|Saigyo]] 11:32, 9 June 2007 (UTC)

== Criticism ==

The last sentence of that passage is non-sense and off-topic. It suggests something that was not stated in its reference in the way represented here.

It should be more like "In some cases, programs that use garbage collection instead of directly managing memory may run faster [4]." OR even completely removed.

I could neither remove nor change it.. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/87.151.43.180|87.151.43.180]] ([[User talk:87.151.43.180|talk]]) 22:29, 1 June 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->

== name ==

rename to object pool? <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/96.26.47.142|96.26.47.142]] ([[User talk:96.26.47.142|talk]]) 04:36, 18 May 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->

== Any reason for the existence of the InUse list in the C# example? ==

It looks like the InUse property is not needed. Any reason we don't take it out?[[User:MissPiggysBoyfriend|MissPiggysBoyfriend]] ([[User talk:MissPiggysBoyfriend|talk]]) 08:57, 21 March 2015 (UTC)

== Pitfalls ==

The pitfalls section (how is that even different than criticism?) is written very poorly. It's like an advertisement for not using it more than actual issues. "You have to be sure to clear all your data!" Welcome to programming. We might as well have big glaring red banners every time someone "reuses" a string variable in a piece of code. If you're smart enough to be reading up on static pools, then you're already smart enough to understand what happens when you leave a dangling pointer or don't clean your data when you re-use it.

Articles should understand their target audience. Differential Equations articles don't need to explain what a variable is. Object pools don't need to explain every way re-using incorrectly reset data can break your program.

The entire section could be reduced to couple sentences merely mentioning the issue (so people remember it) instead of rallying against the use of object pools.

[[Special:Contributions/50.142.138.120|50.142.138.120]] ([[User talk:50.142.138.120|talk]]) 20:03, 14 January 2016 (UTC)