All this talk of patterns has motivated me to dig out my GoF book that apparently never got unpacked when I moved.
One question though, anyone know of any good books that attempt to condense the GoF book into easier reading? My little brother has decided to go into the "family business" of software design and has started to pick up C# recently and I'd like to send it to him as an early graduation gift... R. Joe Reich System Analyst Comcast Communications, Inc. Phone: 248.233.4512 Fax: 248.233.4788 Cell: 734.476.4844 Email: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] > -----Original Message----- > From: Philip Nelson > Sent: Tuesday, March 29, 2005 11:04 AM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Most appropriate design > pattern to use for ... > > It seems to me that CoR adds little value to the > original question if I can remember it correctly ;-) > The fact that it's a chain is not important because > it's unlikely that the list of known processors for > the various flavors of the document are unknown. > Second, this discussion of the CoR came about > because of desire to not have a switch statement > to create the strategies. > > First the use of switch statment is not evil unless > then list of options is long (I use 7-10 as a rule > of thumb) and the list of options is pretty static. > But if you want something more elegant how about > this approach. Assume that the strategy pattern > was used to describe the various vocabulary > processors and that you have a list of strategies > additionally described by interface VocabStrategy: > =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
