Aggregate pattern: Difference between revisions

Revision as of 18:54, 15 October 2005

Revision as of 19:14, 15 October 2005

Line 1:

{{Cleanup-date|October 2005}}

An '''aggregate pattern''' is an important statistical concept in many fields that rely on statistics to predict the behavior of large groups, based on the tendencies of subgroups to consistently behave in a certain way. It is particularly useful in [[sociology]], [[economics]], [[psychology]], and [[criminology]].

In [[computer programming]], an '''aggregate pattern''' is a [[design pattern (computer science)|design pattern]].

Members of a common [[subclass]] are each known to have certain [[method (computer science)|method]]s. These methods return information about the state of that particular [[object]]. It does happen that an application is concerned with an aggregation, or amalgamation, of data from several object of the same type. This leads to code being repeated around the program:

my $subtotal;

Line 65 ⟶ 66:

segmentation and proliferation of interfaces for no good reason. This proliferation

of types prevents aggregation in baskets and containers. Avoid this vicious

cycle.

cycle. Parrots that don't squak are still parrots.

XXX IteratorInterface blurb - aggregation is kind of like iteration in