Wikipedia:Articles for deletion/Aggregate pattern

 This page is an archive of the discussion about the proposed deletion of the article below. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was - kept - SimonP 23:19, May 12, 2005 (UTC)

Aggregate pattern
This page does not seem to be describing a design pattern but more an element of object encapsulation. It seems to be defining an aggregate pattern as a design method that allows data members to be operated on by routines built into their containing object. This is a fairly trivial property of OO design.

Asides from this semantic issue, the article itself is littered with terrible English, with many spelling and grammer mistakes that render it virtually unintelligible. The code examples are entirely unelucidiating, and much of the information is described seemingly from the perspective of a Perl programmer, rather than being a language agnostic description of the methodology. Movint 18:58, 28 Apr 2005 (UTC)Movint

Never listed on vfd, no vote --Dmcdevit 00:53, 4 May 2005 (UTC)
 * Comment. Aggregate patterns are an important concept in many fields (sociology, economics, psychology, criminology)... of course, this article ain't it, and there's enough junk there now for me to think that it would be better to start with a clean slate. -- BD 24 12 think 02:26, 2005 May 4 (UTC)
 * Keep and cleanup as necessary. If someone writes about other aggregate patterns, move this to Aggregate pattern (programming) or somewhere. Kappa 06:46, 4 May 2005 (UTC)
 * Keep the article needs major work. Klonimus 17:48, 4 May 2005 (UTC)


 * This page is now preserved as an archive of the debate and, like some other VfD subpages, is no longer 'live'. Subsequent comments on the issue, the deletion, or the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.