Most (all?) of the post 0.1 mods to CFCdoc were mine, so I couldn't help. ; )
Fusedocs are only useful if you take the time to keep them up to date, just like any other piece of documentation. If you're willing to pay the small cost, they're worth their weight in gold in the long run. Especially if the idiot who wrote the code originally was a version of you that's a year younger. cheers, barneyb On 7/26/05, Paul Roe <[EMAIL PROTECTED]> wrote: > Thanks for your help guys. Those suggestions really ran the gambit and > I apreciate it. > > I am currently using http://www.spike.org.uk/projects/cfcdoc/ for my > cfcs so it was funny that you mentioned that. I could introduce > fusedocs to my group, but I have used them before and they never got > updated or even really used. the most usefull part of them that I have > found it the summary and the change history. > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- 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]
