> I generally agree with this notion but I think it starts to fall apart > with more complex methods. You might have a whole routine that only > gets called one place but is complex enough that there are benefits to > breaking it up into multiple methods that have single concerns. Doing > so makes it easier to debug (the method names provide helpful clues to > follow the chain of execution) and makes it much easier to unit test.
Yeah, this is what I was trying to get at. I don't want to go through hundreds of lines of code at once if I can avoid it. >> Either way, though, the arguments should be clearly defined. > > Agreed. I agree with that too. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342808 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
