After leafing through some more google results….

It's in the docs..

From the compatibility guide:
"4.2.3 CFCOMPONENT
When setting the attribute OUTPUT=”yes”, BlueDragon requires you to enclose all CFML
expressions (#expression#) in CFOUTPUT tags, where CFMX will evaluate CFML
expressions without requiring CFOUTPUT tags."

"4.2.7 CFFUNCTION
When setting the attribute OUTPUT=”yes”, BlueDragon requires you to enclose all CFML
expressions (#expression#) in CFOUTPUT tags, where CFMX will evaluate CFML
expressions without requiring CFOUTPUT tags."

I guess that is why.

;-)

It's possible (likely, even, from what you describe) that a true value on BD means the same as a missing value on CFMX (display the body, but don't act as if it's in a CFOUTPUT block). I very rarely output anything inside CFCs (preferring to return the content as a string), so I can't speak for this discrepancy.

But I have a CFC that displays a small block of HTML.

var = "The string"
In CF6.1 (sorry, I don't yet have access to 7 :-(… ) if you have a variable to display #var# will show as "The string".

While in BD 6.2, #var# in the CFC shows "#var#". I've had to add cfoutput tags so that the vars will display the dynamic content.

Have you seen anything like this?