If a CFC is designed explicitly to output stuff, then it's
an exception. However, if a CFC does that, that ALL it should do. In other
words, every method (except private methods) should be
output="true".
At 01:22 PM 3/16/2004, you wrote:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffry Houser
Sent: Tuesday, March 16, 2004 12:56 PM
To: [EMAIL PROTECTED]
Subject: Re: [CFCDev] OUTPUT="false", WAS: RFC, CFC Best Practices
Jeffry:
I'll assume the other posts answered your first question about why init() is good
My question was why is using the "psuedo-constructor" bad?
As to why OUTPUT="false" is a good thing -- the main reason is that you don't want to break encapsulation.
What do you think about CFCs designed for the sole purpose of displaying data? ( And by you, I mean anyone on the list who feels the need to share)--
Jeffry Houser, Web Developer <mailto:[EMAIL PROTECTED]>
Aaron Skye, Guitarist / Songwriter <mailto:[EMAIL PROTECTED]>
--
AIM: Reboog711 | Phone: 1-203-379-0773
--
My Books: <http://www.instantcoldfusion.com>
Recording Music: <http://www.fcfstudios.com>
Original Energetic Acoustic Rock: <http://www.farcryfly.com>
