General talk about software patterns

[Russell Dodd <rdodd AT hhh.co.uk>]

Ah, OK.

Thanks for the correction. I think we'd missed the point about the
Builder maintaining state of the product - I think we'd assumed (or
deduced or guessed!) that the Director had done that.

Regards,

Rus.

-----Original Message-----
From: Ralph Johnson 
[mailto:johnson AT cs.uiuc.edu]
Sent: 29 May 2003 11:06
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


>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

_______________________________________________
patterns-discussion mailing list
patterns-discussion AT cs.uiuc.edu
http://mail.cs.uiuc.edu/mailman/listinfo/patterns-discussion


**********************************************************************
This email and any files sent with it are intended only for the named
recipient. If you are not the named recipient please telephone/email
the sender immediately. You should not disclose the content or
take/retain/distribute any copies.
**********************************************************************