patterns-discussion AT lists.siebelschool.illinois.edu

Subject: General talk about software patterns

List archive

RE: [patterns-discussion] Prototype and Composite/Decorator and B uilder for Composite

From: Ralph Johnson <johnson AT cs.uiuc.edu>
To: gang-of-4-patterns AT cs.uiuc.edu, patterns-discussion AT cs.uiuc.edu
Subject: RE: [patterns-discussion] Prototype and Composite/Decorator and B uilder for Composite
Date: Thu, 29 May 2003 05:05:40 -0500 (CDT)
List-archive: <http://mail.cs.uiuc.edu/pipermail/patterns-discussion/>
List-id: General talk about software patterns <patterns-discussion.cs.uiuc.edu>

>Without the 'Director', the Builder pattern is just an
>AbstractFactory pattern with an assembled product as output.

A Builder and an Abstract Factory have different interfaces.
A Builder remembers the thing you are building, and has a lot
of operations to add a part to it. It has operations to start
the product and then to finish the product. But the objects
that are parts to a Builder are the actual products of an Abstract
Factory. An Abstract Factory has no state, and doesn't know what
bigger thing is being built.

-Ralph Johnson

RE: [patterns-discussion] Prototype and Composite/Decorator and B uilder for Composite, Ralph Johnson, 05/29/2003