I think what Sean was trying to get at was that an implementation of a design pattern in isolation of a problem it can solve is nothing more than a bunch of arbitrary code. If you have two problems that can both be solved with the same pattern, and you use the same langauge to implement each solution, the implementations will very likely be different. The design pattern itself is merely a guide as to how to best approach implementing a solution. If you go get a book on patterns, you'll always find a problem description preceeding the sample implementation, because without that context (the problem) the implementation is meaningless.
cheers, barneyb On Tue, 4 Jan 2005 09:14:36 +1000, Taco Fleur <[EMAIL PROTECTED]> wrote: > > Example code alone does not teach a pattern! > > Completely agree, which is why I did not provide an explanation, and was > hoping to get feedback from people familiar with the pattern. > The link was just to give an idea of what its all about, I actually read > about the pattern in another book. > > Anyway, I'll go and hide in my corner again and discover the world of design > patterns on my own again, I lost all hope to discuss some of this wonderful > stuff on the cf list and port the patterns to cf for all to enjoy ;-)) > > -- > Taco Fleur > Senior Web Systems Engineer > http://www.webassociates.com -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 9 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189192 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
