I like fusedoc as well - even when I'm using an alternate framework. It makes it easy to get a handle on a particular code block. However, you really must be doing some form of code separation to make it work effectively.
Mark -----Original Message----- From: Douglas Brown [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 07, 2002 10:43 PM To: CF-Talk Subject: Re: Code Commenting I prefer the fusedoc method myself and you just define all your ins and outs to keep track of the application. you can find more examples on http://www.halhelms.com IE: <!--- <fusedoc fuse="FBX_Switch.cfm"> <responsibilities> I am the cfswitch statement that handles the fuseaction, delegating work to various fuses. </responsibilities> <io> <in> <string name="fusebox.fuseaction" /> <string name="fusebox.circuit" /> </in> <out> <string name="myString"/> </out> </io> </fusedoc> ---> "Success is a journey, not a destination!!" Doug Brown ----- Original Message ----- From: "Paul Giesenhagen" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Sunday, April 07, 2002 8:29 PM Subject: Code Commenting > Does anyone have a good resource(s) for examples of good code commenting? > > I am trying to find some various ways/practices people are commenting code. > > Thanks > > Paul Giesenhagen > QuillDesign > http://www.quilldesign.com > SiteDirector v2.0 - Commerce Builder > > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
