For those on the list who aren't interested in the squabbles over whether or not CFCs are a "good thing" and just want some sound advice I figured I'd summarize the discussion about the OUTPUT attribute this way:
Unless you are absolutely sure you want to output directly in your CFC (which you should almost never want do) you should always set output="false" in your CFFUNCTION tags. Personally, even if it's a bad design decision to have "tri-state" logic, it seems silly to say people didn't know when it's very well documented exactly how it works. Since you'll want to have output="false" in almost all cases anyway, this hardly seems like the kind of show-stopping issue with CFCs you make it out to be. <rant> And lest anyone be scared off by the FUD, CFCs have been successfully used in a huge variety of applications with great success. They are very useful to OO veterans like Sean and his team at MACR, but I have seen them used with great benefit by more typical CF folks who gain tremendous benefits from them in the natural structure they bring to their code and the ways in which they promote separating "logic" from "display" -- whether they have interfaces and the other trappings of Java is an interesting academic discussion, but for those of us just trying to build applications that actually work, are actually maintainable, and actually get done in a reasonable amount of time CFCs are the best thing to happen to ColdFusion since the invention of custom tags. </rant> - Nathan ---------------------------- Nathan Dintenfass [EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
