> > The tristate boolean is the output attribute. If it's > missing, it treats the body as normal template text (need > CFOUTPUT to output), if it's set to true, it treats the body
Not true, I mean the first part. Consider: <cffunction name="test"> hi ray </cffunction> <cfset test()> This will output hi ray, even though I did not include <cfoutput> tags around hi ray. > as if it's surrounded by CFOUTPUT, and if it's set to false, Not true... exactly. You say it treats the body as if surrounded by cfoutput. That implies that if I do <cffunction name="test" output="true"> #foo# </cffunction> That foo will be displayed. This is not true. Instead you just get #foo# > it treats the body as if it's surrounded by CFSILENT. Now that is true. > CFCs do have their problems (you mentioned three), and while > I realy like them, I'm totally with Matt here. Somone had > their head up a certain orifice on this one. I completely disagree. CFCs are the best tool yet in CFML. Are they perfect? Heck no, but to say that the designer had their head up their ass is a bit extreme. ======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ---------------------------------------------------------- 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]
