> Im having a hard time convincing my team about > the benifits of modularising code, particularly > the use of <cfinclude>
Uh oh (;-)... Recently, I needed to make a change to a section of a fusebox app that I hadn't looked at for a while, and it was wonderful. One known file shows which files get called, in what order, for each different request in this area. This file here is the main query, this one queries for some related manys. This other file processes the 'many' query results for display, this one does the display itself. That one does the update query... Each file has a distinct, isolated purpose, with documented ins and outs, and no extraneous stuff to think about or ignore. You can find the code you need to look at quickly and easily. Above all, each bit of code fits nicely in your brain, which is Really Good. It was a beautiful thing. Dave Merrill ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
