> > 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. > > > Which is completely consistent with how CFML is handled when > it is not > in a cfoutput tag, so it is true.
Ah, it was a misreading of what Barney said - he said, "need CFOUTPUT to output", and I read that as "need CFOUTPUT for _anything_ to output", not "need CFOUTPUT for variables to show..." > > 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# > > > Try the code and see, foo will be displayed. Yep, mistake on my part. > Read the documentation Ray and you will see what we are talking about > it. It doesn't make sense, but it IS the case. > Agreed. This _is_ confusing and I'm going to blog it so others are aware. -ray ---------------------------------------------------------- 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]
