Design Patterns discussion

["Mikal Ziane" <Mikal.Ziane AT lip6.fr>]

I guess that if class Client wants to use some methods of classes A1... An
uniformly (hypothesis of Composite) then it is natural that class Client use
"new" uniformly too and hence rely on Prototype.

It is not necessary if the goal is simply to use specific methods uniformly
(e.g. "draw") to hide the loop involved by calling the method on parts of a
composite (e.g. drawing a figure involves drawing its parts).

But if the goal is to decouple class Client from the existence of classes A1
... An (which implies using all their operations uniformly including "new")
then a creational pattern like Prototype of Factory Method is useful if not
necessary.

-----Message d'origine-----
De : 
gang-of-4-patterns-admin AT cs.uiuc.edu
[mailto:gang-of-4-patterns-admin AT cs.uiuc.edu]
 De la part de Yves Roy
Envoyé : mercredi 28 mai 2003 19:25
À : 
gang-of-4-patterns AT cs.uiuc.edu;
 
patterns-discussion AT cs.uiuc.edu
Objet : [gang-of-4-patterns] Prototype and Composite/Decorator and Builder
for Composite

Dear suscribers:

I have 2 clear and simple questions:

1) The GOF book mentions in the Related Patterns section of Prototype
pattern (p. 126) that "Design that make heavy use of the Composite and
Decorator patterns often can benefit from Prototype as well".

My question is, how, exactly? Any simple C++ examples illustrating would
be welcome.
tinfo/gang-of-4-patterns