I know what most of you are trying to get at (I read the book too) "Don't use design patterns just for the sake of it". I'm not interested in discussing that, a pattern solves certain problems, lets just say I have all those problems that this particular pattern solves!
Aaron you are spot on. But as Sean already pointed out, this is not the list to discuss it. And yes a site dedicated to design patterns for CF would be nice (any volunteers to help ? ;-)... -- Taco Fleur Senior Web Systems Engineer http://www.webassociates.com -----Original Message----- From: Spike [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 January 2005 12:21 PM To: CF-Talk Subject: Re: Typesafe enum design pattern (another go) That's not describing the problem. It's describing a solution. Why do you need constants? Why do you need them to be in a class/cfc? Why do you not want the public to be able to modify any data and who do you define as the public? Why do you need to be able to loop over the constants? Spike Taco Fleur wrote: > The problem: > > I need a class that represents constants I don't want the public to be > able to modify any data I need to be able to loop over the constants > easily > > Basically quoting what problems the pattern solves.. > > -- -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189203 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
